Unreliable database verification

[Naith]

Hey,

Have any of you experienced a situation where you commit changes to the database, and verify the report, and the report only acknowledges some of the changes, whilst appearing to invent others?

I have several stored procedures against which I have reports running, periodically verifying the database. But, instead of getting up to date with the datasource, the report appears to mistreat the stored procedure characteristics: datatypes change from string to number; string(20) fields are read as string(5)...

This affects more than one report, so I'm not sure it's down to a corrupt rpt file. Any driver related clue you could give me would be a great help.

Thanks,

Naith

 

[synapsevampire]

What connectivity are you using? You ask for driver information yet you don't share what driver that you're using.

And what database, version? Version of Crystal?

Perhaps if you use OLE DB instead of ODBC or vice versa you'll see some improvements. And remember to only use the CR supplied ODBC drivers.

Good luck, sounds like an annoying problem.

-k