ODBC Error:.......Invalid Object Name 'table name'

[yehong]

Hi,
I have a report that is using about 6 subreports. I have set the location of each sub report and the main report to new tables, one by one. Still when I run the report I get the above error.
Any help is highly appreciated.

 

[Turkbear]

Hi, What database and version ( if applicable)

Any table names explicitly set to 'table name' ?

View the location ( set location ) source in each subreport to confirm it has been set correctly.

 

[yehong]

SQL Server 2000. CR 8.5. I have confirmed that each subreport and main reports table is pointing to the new database tables.

Could you explain what did you mean by:
"Any table names explicitly set to 'table name' ?"


Thanks,

 

[vidru]

Try picking them off one by one to see if it's one subreport in particular that's causing the problem. I'd start by suppressing all of the subreports, and making sure the main report can run without errors.

Once you've got the main report running, unsuppress the subreports one at a time, and refreshing the data.

-dave

 

[yehong]

Just did that. Supressed all subreports. Still getting this error.
Main report is using 4 tables. I have set the location of each table one by one to the new tables in the new database. Still getting this error. The error is pointing to the name of the first table appearing in the list of setlocation box. I am trying to figure out since last night and still no luck. very frustrated...

 

[vidru]

What happens if you try to create a new report using that table?

What's the table name? If the table name containse a SQL Server reserved word, that could cause some problems.

-dave

 

[yehong]

I created another report and select the same table and it runs ok in that report. The table name is not a reserved word. It is ce_EmpInf.

 

[synapsevampire]

Rather than using Set Location, use Database->Verify Database.

If something is wrong, it should let you know.

Perhaps it's your ODBC driver, are you using the MS SQL Server ODBC, or the CR supplied SQL Server?

You might try switching.

-k

 

[yehong]

Ok. Finally I was able to discover and fix the problem. The problem was in the Sql query. I opend the query in Show SQL Query, removed everything and ran the report and it ran without any errors. I really appreciate you guys for your support.

Thanksl