Memory crash when creating FoxPro db

[rockofvictory]

I provide IT support for my company. I don't use Crystal Reports, so any help with this problem would be much appreciated!

She (the user) has created these same kinds of reports many times in the past but it is not working today for some reason (she's tried several different computers, too).

Crystal Reports 7 comes up with crw32.exe Application Error (instruction at "0x6b06d37d" reference memory at "0x00000048"...) after clicking on the FoxPro database that she wants to use (Standard Report Expert > SQL/ODBC > Log On Server). This database can be read from without any errors; it's only today that she can't write to it without getting this error.

~

http://Zepfanman.com/Equality

 

[IdoMillet]

Is the problem occuring when running old reports? If so, try to open these reports in design mode and before previewing, use Database, Verify Database.

hth,
- Ido

CUT, Visual CUT, and DataLink Viewer:
view, e-mail, export, burst, distribute, and schedule Crystal Reports.

http://www.MilletSoftware.com

 

[rockofvictory]

I've got a similar error on the same machine, same program (these are always in Crystal Reports Designer, too). Now, if a completely new Standard report is being created and I choose the datapath for the Visual FoxPro ODBC driver, I get the referenced memory error again. Occasionally, it will show "[MS][ODBC Visual FoxPro]Not a table" and just revert back to the main CR program.... I'm definitely at a loss on this one. The error has started today, even though it worked yesterday! It happens on multiple machines that I have CR installed on (trying to create a report in the same directory), as well.

~

http://Zepfanman.com/Equality

 

[dtempleton]

What driver is being used (go to "Database" --> "Convert Database Driver...")? Are all of the tables coming from the same database (go to "Database" --> "Set Location")? Are stored procedures now being used?

 

[synapsevampire]

The tables could be locked, I've had similar problems with that.

I had ignored the original post as it stated a problem when writing to a fox table. CR isn't a good idea for writing to a Fox table, in fact it can't write to an existing table, as it can only create a NEW table.

You might try using a dbase odbc driver as well, depending upon your version of Fox.

Not taking the time to post obvious technical information like that will get many people to ignore your posts.

-k