Verify Database Hangs CR 8.5 (BASIS ODBC Driver)

[reporting]

One of my clients has a couple of reports that he runs all the time. These reports only use 2 tables. At their request, their BASIS programmer made some changes to the database. Really minor, adding one field to one of the tables, adding a couple of fields (one with an index) to the other.

He wants to add those fields to his reports but couldn't see them so he asked me what to do. I explained the use of the Verify Database menu item and he tried it. Nothing happened. 15 minutes later, CR was still 'Not Responding'. So it was 'End Task' time... He tried a couple more times and the same thing happened!

I checked the CR KBase and could find nothing about CR hanging on a Verify. My own experience is that Verify Database takes a couple of seconds, even with complex database structures! However, BASIS ODBC drivers are not the usual drivers I use...

Any ideas on this? Anyone use BASIS ODBC for reporting and have the same probs? Or use BASIS ODBC without the same probs?

There is an added complication: he uses French Windows 2K Pro & French Crystal Reports... FYI, the system info is as follows:

Windows 2000 French SP 2
CR 8.5 French Prof version 8.5.0.219
BASIS ODBC Driver ver 2.32

Thanks very much,
John Marrett
Crystal Reports Trainer & Consultant

http://www.e-reporting.ca

 

[synapsevampire]

Can they create a new report with those fields?

If so, the report may be corrupted, do they have an earlier version of the report?

You might also try a OLE DB for ODBC and see if that helps.

Is it possible that these new fields are unsupported by Crystal?

Good luck with it, a bit too obscure for most I think.

-k

 

[reporting]

Yeah, it is pretty obscure. I was actually hoping that someone here had experience with the BASIS ODBC driver and knew a workaround for this problem...

I'm going to be there in 10 days for a training session so I'll take a look at it then.

By the way, I don't think that it is corrupted reports: the reports still work fine. They just can't add the new fields to them...

Thanks very much,
John Marrett
Crystal Reports Trainer & Consultant

http://www.e-reporting.ca

 

[lyanch]

You might try set->location (to the same place it was) instead of verify. Combining this with a second set up of the ODBC driver may work. set->location to new odbc.. then set->location back to the old one..

Lisa

 

[reporting]

Very interesting.. Hadn't thought of that!

Thanks very much Lisa!
John Marrett
Crystal Reports Trainer & Consultant

http://www.e-reporting.ca