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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"xbase Error: Bad user specified Key Expression"

Status
Not open for further replies.

MHPGuy

IS-IT--Management
Mar 14, 2002
143
US
Does anyone have any insight into the following error:

"xbase Error: Bad user specified Key Expression"

followed by

"Error detected by database DLL"

It started happening with one report and has begun with several others. Many of the reports are still working just fine. The database that the reports are using is fine, and hasn't experienced any recent errors. The system being used to run the reports doesn't seem to affect the errors- I've tried running the report on multiple machines and I get the same error.

Any guru help is greatly appreciated!

Michael Phipps
Technical Business Analyst
Mercy Health Plans
 
I experienced this error message before. I used Crystal Report and Goldmine DB. What I did was search my machine for a CRPE32.DLL and found that the CRPE32.DLL file located in the Goldmine dir was older and smaller than the CRPE32.DLL file located in Window dir. I replaced the file in Goldmine dir with the one in Windows dir and my problem is solved. CD has a utility called Module. Use this utility to determine what DLL and version of DLL are being used by the reports. Hope this will lead you to something.
 
It looks like Ken Hamady has found the solution to this problem- quite awhile ago! Now, does anyone have the file...?

1) Error Reading Goldmine Tables.
The Xbase DLL (P2Bxbse.dll) is incompatible with some Xbase formats, specifically those used by Goldmine 5.0. The bug appears whenever you try to link tables in a one-to-many relationship, going from "one" to "many". This worked fine in V8, but doesn't with V8.5. You get a message that says:

Xbase Error: Bad User Specified Key Expression

The workaround is to use the old V8 dll file. First rename the V8.5 dll and then put the V8 dll in the same directory. If you do an Windows Explorer search for this file name you may find both versions already on your PC in different directories. I did. Crystal Tech support also suggested using a HotFix for their Export Dlls, saying that this 'might' fix the problem. I didn't bother with the Hotfix once I got the V8 dll to work. If you want the HotFix and the latest export dlls, contact Crystal Tech Support.

Michael Phipps
Technical Business Analyst
Mercy Health Plans
 
And, to make life easier for everyone, here is a location where you can download the file. It's in Italian, but you can figure out how to get it, and it works perfectly!

Michael Phipps
Technical Business Analyst
Mercy Health Plans
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top