Error:20533.Unable to Open Database

In my project I have used VB 6 and CR 8. In my machine the application is working fine. When it was loaded in the customer machine with windows 98 OS, when the report is clicked, it shows the error 'Error:20533 Unable to Open Database'. The Back end used is MS Access. Anybody pl. guide me to install my project? What to do and how to do?

Pl. post your reply due to urgency.Case 1)If u r running ur exe at client side u must place ur Database at the location u have given to ur DSN
Case 2)If u have installed ur setup at client side and just want to replace exe then check whethere u r replacing ur exe in the folder that has been installed on m/c|||Tried. But getting the same error.|||Open the Report and Do verify Database and map the columns if any|||Verify database. In my machine it works. I haven't installed the CR in the client machine. HOw to set right this problem. Is it necessary to load the CR in the client side? Pl. help
Meenakshi.R|||Did you use DSN to connect to CR?|||I haven't used any DSN for CR inthe client side. How to create that DSN for CR? pl. explain.|||How do you connect CR to database? Did you use OLE DB?
Create a DSN pointing to that DB and design reports. In the Client system create the same DSN and point it to that DB.

Otherwise refer this
http://www.businessobjects.com/support/default.asp

Error: The MDX function ROOT failed because...

I'm having problem calculating sales for all customer minus certain occupations.

This Adventureworks query is something like what Excel 2003 produces.

Code Snippet

WITH MEMBER [Customer].[Occupation].[Exclude Occupations] AS

'AGGREGATE({

[Customer].[Occupation].&[Clerical],

[Customer].[Occupation].&[Management]

})'

MEMBER Measures.[Other Occupation Sales] as (ROOT(Customer), [Measures].[Internet Sales Amount]) - [Measures].[Internet Sales Amount]

SELECT

{Measures.[Other Occupation Sales]} ON COLUMNS,

[Product].[Category].[Category].MEMBERS ON ROWS

FROM [Adventure Works]

WHERE

([Customer].[Occupation].[Exclude Occupations])

Error: The MDX function ROOT failed because the coordinate for the 'Occupation' attribute contains a set.

If you delete this line, the query works!

[Customer].[Occupation].&[Clerical],

Does anyone know what this means? Is there another way to get Excel to formulate an equivalent query?

The problem is because there is a set in the current coordinate, and Root has problem dealing with it (although it shouldn't!). The best solution is to replace Root(Customer) with [All Customers] - which will have exactly same functionality, better performance, and won't generate the error that started this thread.|||

Yes, I replaced Root(Customer) with [Customer].[Occupation].[All Customers] and it works. The problem is that I wanted to create a general purpose calculated measure that would override every attribute in the customer dimension with "All". I thought Root did precisely that. If I can't use Root() then I will need to remember to update this calculation every time an attribute is added or removed from the customer dimension.

Thanks for the input.

|||

> The problem is that I wanted to create a general purpose calculated measure that would override every attribute in the customer dimension with "All"

[All Customers] does exactly that ! There is no need to update your calculation every time new attribute is added, [All Customers] (in any hierarchy of customers dimension) will automatically move coordinate to All member in every attribute.

|||

Try my AdventureWorks repro with [All Customers] instead of Root(). It doesn't work. It doesn't replace the aggregate set of occupations with the All tuple. I end up with zeros in the results because [All Customers] is doing absolutely nothing for me.

The only way I got it to work was with [Customer].[Occupation].[All Customers]. This member does, in fact, replace my aggregate set of occupations.

Put that in your pipe and smoke it!

I'm curious how [All Customers] is defined to work (vs. Root()).

|||Of course - you are right. I don't know what I was thinking. What I said is only true when dimension has single hierarchy which includes all attributes, which is obviously not the case for most of the dimensions, especially Customer.|||Thanks for the help. At least I have a work-around for now. It would be nice if Root(dimension) did the same thing as change coordinates to [All Customers] on every attribute. Maybe in the next version...

ERROR: table don't support this operation

hello all,

this query causes error on some servers (sql2000 sp3). on our development server is this ok. we have restore the database from customer server to the development server, this is ok too. we don't know which configuration on the server can change to solve the problem.
-
select distinct V.Vereinsname as Vereinsname, V.VNr as VerNr, V.PLZ as PLZ, V.Ort as Ort, V.Strasse1 as Stra?e1, V.Strasse2 as Stra?e2, '0' as Sel
, V.Statusfeld01, V.Statusfeld02, V.Statusfeld03, V.Statusfeld04, V.Statusfeld05, V.Statusfeld06, V.Statusfeld07, V.Statusfeld08, V.Statusfeld09
, V.Statusfeld10, V.Statusfeld11, V.Statusfeld12, V.Statusfeld13, V.Statusfeld14, V.Statusfeld15, V.Statusfeld16

from VRMWSTD V
where 0 < V.VKrNr
and V.VKrNr in (1)
order by Vereinsname

-
the message in german is: "Tabelle unterstützt diese Operation nicht."

many thanks in advance

duong

Have you checked the index?|||just a question but why do you do this -
where 0 < V.VKrNr
and V.VKrNr in (1)

and not simply

where V.VKrNr = 1

I don't know. . . sql might optimize it out, but seems like overkill.|||Could you please post a simple repro script? The error message looks like a client library message and not SQL Server. It could be that you are trying to add/update rows in the datatable or recordset for example and it is not supported. This can be due to the nature of the SELECT statement (use of DISTINCT and ORDER BY clauses) which will make the resultset read-only.