Macola 7.6.100 and Crystal v6

[dgillz]

I have a client still using crystal 6 and they upgraded to 7.6.200 and the suddenly have a problem when they try to write a new crystal report.

They are not seeing the correct file names in the .ddfs For example, instead of "APALTADR_SQL", the see "TADR_SQL".

Has anyone ever experienced this and if so what is the solution? I have already tried replacing the .ddfs with ones that work fine for me in versions 7 and 8.5.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[dgillz]

Typo. The upgrade was to 7.6.100, not 7.6.200.

There are enough things wrong with 7.6.200 without me having to invent one.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[MacolaHelp]

Sounds strange. I have someone still using crystal 6 w/7.6.100a & I just had to write a report last month & it worked fine. Maybe you should reinstall crystal? I have this vague memory of something like that happening w/version 5 crystal 16 bit where it couldn't/wouldn't recognize file names > 8.3. Is the client on an old netware, too? Some netware versions didn't like long file names, either.

 

[dgillz]

No netware, they are running on a windows 2000 server.

Already tried reinstalling crystal.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[kscheeler]

I'm thinking back here since I don't have crystal 6 installed anymore but did 6 have both a 16bit version and a 32bit version?

Is it a local install or a network install with then installing the client from it?

Do you get the same type of error if you tried to write a report using ODBC vs. the native Btrieve driver?

Kevin Scheeler

 

[dgillz]

I have tried this both with a network install and a local install of crystal with the same results. ODBC is where I am going next.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[crystalreporting]

Should work fine. Does the problem occur with both Native and ODBC connections?

Peter Shirley

http://www.linkcorp.com

 

[MacolaHelp]

Can you see the full file name if you look at the legacy tables rather than _sql? Is this a pervasive site? Are they using an old version of btrieve?

Peter: v6 was the first CRW that was 32 bit, v5 was 16 bit. I think we had to upgrade to at least v6 to see the _sql table names. v5 couldn't see/read them much as Don has described for his site.

Don: maybe they should just buy a single user 8.5? It's not all that spendy, even for a small company.