CR with VFP data

[ipazzo]

Hi friends,
I have user CR to make reports for my application and
now i have this problem:

On my pc all works fine but on others pc ....

This is my field definition

This is data in the table

This is what i see in the report on my pc

and this is what i see if i install application on others PC

Where is the problem ?????
Please help me!

 

[craigber]

I'm guessing here, but are their differences in the regional setup between the two computers? Could something be wrong with the number formatting (commas and decimal points) between then two?

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[ipazzo]

No Craig, there are no differences in the regional settings.

The only difference there are between the computers, i think is that on my pc i have installed CrytalReports and on the others not.
Tomorrow i try installing CrystalReports on one of the others pc, but in any case i must find the rigth solution because i dont wont to distribuite CR with my application.

 

[synapsevampire]

I think that Craigber may be correct.

At any rate, you might try to ensure formatting by right clicking the numeric field->Format Field, and using a custom number format.

The alternative would be to convert it to a text field for display purposes:

totext({table.quantita},0,"&quot

-k

 

[craigber]

How are you accessing the data? Direct access, ODBC? ADO? Is the data from the same table in both cases?

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[ipazzo]

@synapsevampire
in my original report i used a custom number format to see only the integer part of the number (12,00 --> 12 ) on my pc that worked good but on others i see only zeros.

@craigber
data is accessed via ODBC, and is from the same table

 

[ipazzo]

WOW.....

i have solved the problem.

after i had installed CR on a pc with the problem, the problem continued. So i taked a look on the about box of CR in the OtherInformation dialog box and compared all DLL versions from the two PC. I have found same differences, and after that i have replaced ( after a backup ) all the different dll's. That solved my problem.
I have restored the original dll's and then replaced again with the different ones but one at a time, so i have found the dll causing the problem was:

system32\p2sodbc.dll 8.6.0.92 (bad results on report)
system32\p2sodbc.dll 8.0.1.0 (good results)

Now i put the good dll in the same path as the application and all works fine.

Thank you all for your patience in helping me!



Vito M.
---------------------------------------
When you build a TEAM, try always those that they love to win. If you do not succeed to find them, then try those that they hate to lose. Ross Perot