database table cannot be opened

[pmgatwork]

Hi all
I have some crystal reports linked to Sage Line 100 (odbc)
Every time I run thiese reports I get the above error.
If I respond No to the message - remove table from report - the report works fine

Crystal 9

Any ideas

thanks
peter

 

[TheBlondOne]

Are you saying that if you remove the table the report runs fine or are you saying if you click on "No" when you get the error message the report runs fine?



-Steve


"if at first you don't succeed, sky diving is not for you"!!! )

 

[pmgatwork]

Hi Steve
No I dont reomve the table only say no to the message. I can then run the report and it is fine. However if I try to reload this report and rerun then the same applied.
If I try to set the datasource location I then get a data object cannot be accessed error

Peter

 

[TheBlondOne]

I presume that you recieve the same error message if you try to verify the database??

Has the table changed in anyway on the DB side?

-Steve


"if at first you don't succeed, sky diving is not for you"!!! )

 

[pmgatwork]

Steve
Yes If I try to verify then I get the dabase cannot message. If I then click no to remove it says that the database is up to date but it still gives the same errors on reload
No the table has not changed

 

[TheBlondOne]

Sounds like somethings got corrupt. Is the table your using a table or a view?

Also have you tried creating another report but just using that table, and adding a few fields from that table into the report. Does it run?

-Steve


"if at first you don't succeed, sky diving is not for you"!!! )

 

[pmgatwork]

Yep tried doing exactly that. It does this will any report using files in the sage line 100 system
peter

 

[TheBlondOne]

Sorry might be me being a bit blond (hence the name) but are you saying that the table doesn't work even when you create a new report with it?

-Steve


"if at first you don't succeed, sky diving is not for you"!!! )

 

[pmgatwork]

I get the same message but after I click and respond to the message the reports then run. The trouble is that I want to svedule these reports and I cant because of this error
Peter

 

[TheBlondOne]

Thats really strange Peter. Has the table got security locks on it for certain users, i.e datareader, datawriter disabled?

-Steve


"if at first you don't succeed, sky diving is not for you"!!! )

 

[pmgatwork]

the odbc is read only