I keep getting this error on a rpeort , ( that has no custom veiws or anything ) just a basic odbc report .Any ideas what could be causing this error?
This same report works on three other machines and fails on one specific machine.
well we have a broland report manager custom front end running crpe32.dll ( which seems o be the problem ).Odbc is provided by pervasive database and we are using 8.5.
Sounds like a job for whoever created the front end for you.
If it functions on 3 machines, and other reports function on the 4th but not this one, I'd suspect a missing DLL that the report is using that other's are not, such as grqaphing, etc.
The above whitepaper describes that error reasonably well, there are a myriad of possible problems, including MDAC, wrong ODBC, etc.
One possible scenario that we run into all the time with our customers, is getting 534 errors on standard reports we ship with our product. Our customers can customize the database so when they change a default field name or there is a database structure change or a field that is referenced in the report is not in the database the report is being run against, 534 errors are generated. We often have to verify reports against the database the customer has. Just another idea to check on and one of the simplest causes and solutions for 534 errors. If the databases are local on the machines, it could be the one specific machine you are getting the error on has slight database structure differences from the other machines.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.