dll error depending on how I arrange tables

[teamssc]

I have two tables (dbase) that I am including in a report...

If I create the report with Contact1 then ContSupp I get two errors
1) xBase error: bad user specified key expression
2) error detected by database dll

If I reverse the creation steps and insert the ContSupp first then the Contact1 the report works...

Can someone explain why the order might matter?

Thanks,

Don

 

[kenhamady]

This is a bug in CRv8.5. I discovered it when I upgraded to v8.5 from v8 and my Goldmine reports stopped working.
See the following:

http://www.kenhamady.com/news0110.html

Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB

http://www.kenhamady.com/

tek@kenhamady.com

 

[teamssc]

There is a list of DLL's for GoldMine 5.7 (and my guess is they would work with 5.5) and Crystal 8.5 I can post these for you this weekend... I'm on the wrong computer now...

We are successfully running 8.5 reports with GM 5.7 and running them in Automated Processes....

Can you address the need to insert databases in a specific order?

Thanks Don

 

[dgillz]

Do you have smart linking turned on? I have seen smart linking, which I have never liked, react differently based on which database is added first.

Try both report again and see if the links are identical. I would not be suprised to see that smart linking is not all that smart in this case. Software Training and Support for Macola, Crystal Reports and Goldmine
714-348-0964
dgilsdorf@mchsi.com

 

[kenhamady]

I am also successfully running GM reports from v8.5 - but to connect to the Dbase files I use the v8 version of the P2Sxbse.dll.

The bug in P2Sxbse.dll is what causes it to only work in one direction. The v8.5 version of this dll apparently can't link to a non-unique Dbase index, so when you link from one to many it fails, but when you go from many to one (or one-to-one) it works. You should find the same behaviour if you try ContHist or Cal.

When I reverted back to the v8 version of the dll, I was fine. This might have been addressed in the v8.5 HotFix. Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB

http://www.kenhamady.com/

tek@kenhamady.com