Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Verifying reports 1

Status
Not open for further replies.

kuling

Programmer
Oct 2, 2001
12
SE
I have a problem with verifying reports made in CR8.5. I got the message "The database is up to date" but when I run the report in my application I get "Error: 534 Error detected by database DLL". When running the reports in CR I get "Betrieve [22] Data buffer length".

I noticed that when I remove the database from the report and then add it again the report works fine. But this workaround is time-consuming because its many reports in question.

We use Pervasive SQL 2000i SP4 as database manager.

Does anyone knows something about this bug(?) in CR 8.5?
 
A verify looks for changes in the tables (new fields, etc), but this sounds like a driver problem.

Did the reports work at one time? Was something changed, like an upgrade of some kind? Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB
tek@kenhamady.com
 
Our old application was developed in Delphi 3 and the new application is developed in Delphi 5.

But the fact that the report generates "Betrieve[22] Data buffer length" when running it trough CR 8.5 is not affected by the change of Delphi version as I see it.

When we built the new database we used Pervasive 2000i SP3. The old database is developed in Pervasive 2000 SP2.

My conclusion is that the new database causes the trouble. And isnt the "Verify database"-command in CR is the only command to use when the database has changed?

/Confused programmer

 
Are you using ODBC connection or the native file.ddf btrieve connection? I would try both if one is having a problem. Software Support for Macola, Crystal Reports and Goldmine
dgillz@juno.com
 
Thanks dgillz. It didnt work with the ODBC-connection, but when I changed back to the Betrieve-driver I got the message "...has changed. Proceed to fix up the report?" You bet I will, I answered;-)

This is very strange, why didnt I get the above message when I verifyied the reports? CR moves in mysterious ways, dont you think?
 
I do not know why it did this. What happens if you now change back to the ODBC driver? I suspect it will work. Please post and let us know. Software Support for Macola, Crystal Reports and Goldmine
dgillz@juno.com
 
I was wrong. It did work with the ODBC-driver.

But the fact still stands: CR doesnt "Fix up" the report before you change the driver. Very strange!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top