xBase MDX file not wrking in CR11

[BlindPete]

Hello,

I am rather frustrated. The reports use xBase DBF/MDX the reports work like a champ in CR10. However in CR11 the joins do not work correctly. If i delete the MDX files the reports work. Anyone have any idea what I am doing incorrect?

-Pete

 

[synapsevampire]

I thought that MDX files were index files, why are they being used?

And what connectivity are you using, if direct try switching to ODBC and vice-versa.

-k

 

[BlindPete]

Yes, MDXs are index files. I am connecting to each table directly, sadly ODBC is not an option for this environment.

Doing an unenforced left outer join returns very few (about 1%) of actually matches. Doing an inner join returns only about 1% of matches. What is so darn frustrating i the same databases work fine with CR10.

I can match the CR10 output only if rename or remove the MDX files of the joined table.

-Pete

 

[synapsevampire]

It sounds as if the native driver is misunderstanding the indexes and sending the wrong query, assuming that's how you're connecting.

Perhaps the unenforced result set is due to padding or data types, try trimming and make sure that you have like data types.

Also make sure that you issue the Database->Verify Database to allow Crystal to resolve differences that it recognizes.

-k

 

[BlindPete]

Well I have danced around it several ways. I am utterly convinced is CRXI bug. The MDX do not cause this issue with CRX. Verifying the database had no effect. The fields types matched precisly. I also tried trim, and I also attempted various null state scenarios. The end result is the same. Remove the MDXs and it works fine. CRXI BUG.

As a work around I ended up creating an ODBC connection using the MS DBase IV driver. It works it is going to cause problems with the client and add to the configuration script. I wish we could go back to CRX but dvelopment can not easily switch back.

Thanks for your suggestions.

-Pete

 

[synapsevampire]

Not sure which versions of dbase the native connection is supposed to support, but at least you have a workaround, albeit problematic.

I guess it's worth a try applying the latest service pack as well.

-k