Set Location

[dreman]

I am using CR 8. using SQL server.
First I create a report using dumy table. It works.
But when trying to set location to the SQL server it finds it with no problem, however when executing report an ERROR with 'GENERAL SQL SERVER ERROR' CHECK MESSAGE FROm THE SQL SERVER
then click OK another ERROR = 'ERROR DETECTED by database DLL'
Any hints why ?
(What I did in previous reports is I went and created the report from scratch with SQL server it is fine. It seemed that set location is giving me a problem. Please advise. Thank you.

 

[nomi2000]

Dear use follwoing code
'Database Setting For Main Report
For intTables = 1 To ReportObject.Database.Tables.Count
ReportObject.Database.Tables(intTables).Location = ReportDatabaseName & ".dbo.Proc(stp_ORD_GetOrderItemsByOrderID;1)"
ReportObject.Database.Tables(intTables).SetLogOnInfo ReportServerName, ReportDatabaseName, UserName, Password
Next intTables

if u have subreport then u also have to check out for it
Regards
Nouman

 

[Ngolem]

Ok...let me see If I got this

You have created a report with a dummy table...is this an Access table or Oracle?

then you are using set location to convert the report to another database...are you maintaining the same database type? ie. oracle to oracle .... Access to Access?
Not sure that you can mix/match databases.

I'll assume the table structures are similar between the 2 reports

First choose Database|set location and select one table and press the set Location button.

Now you select the database and coressponding table in it to the Dummy table...then press Set

If there is a problem mapping the dummy table to the new table a form comes up for you to do this manually (eg. some field names may be spelled differently)

Then Crystal asks to propagate this across all tables (I like non questions...of course you do!!) and if there are any problems then you will have to map manually these tables as well.

THE ONLY PROBLEM I FOUND IS Subreports....Crystal says that it propogated the changes across subreports as well but sometimes this doesn't happen....check each subreport out so that it is pointing at the correct database .... if they aren't then repeat the process for the subreport.

Otherwise it should work fine...maybe verify the DB before using...Jim

 

[dreman]

thanks guys for the advises But:

- I verified Database (table). updated ok
- I propagate table to the same location of the set table. (i have about 5 table linked to each others).
- I have no subreports.
- I do not use aliases instead i am using views tables
and I still get the same error.
Dré

 

[Ngolem]

"- I do not use aliases instead i am using views tables"

this may be your bad guy. I'm not sure. since Views are executed queries on the database and maybe they aren't getting the right info...fishing here...

You didn't say you were going from Oracle to Oracle, Access to Access...you aren't trying to go from one database type to another are you?

Did you veryify the database AFTER you completed the Set Location? or just before.

 

[medox]

Hi Dreman,
I've been getting this error sometimes too. The best way that I found to debug it is, after you get the error, go to Database/show SQL query (on Crystal Designer), copy the existing query and paste it into SQL query analyzer... clean the incompatible quotes and try to run the query. Most of the time I can figure the error out with more friendly messages that comes from Query Analyzer!

///edox