Error 20500, Not Enough Memory for Operation

[HuskerMark]

I have a VB6 application which connects to an Access database, and then prints reports using Crystal. This application has run successfully in many environments. In one location I am now receiving an error 20500 - "Not Enough Memory for Operation" when trying to print the crystal report. The software in this location has worked correctly in the past, and there are two other machines in that environment connected to the same database and using the same reports- which are still working fine.

The online knowledge-base info I have found mentions only two things: making sure the database and reports are in the same location (which is true in this instance), and checking the database workgroup (system.mdw) configuration. On my development machine I have the db workgroup set to my application's .mda. On my test machine (which doesn't have Access installed), the sysdb32.exe doesn't bring up anything, and the app. works fine, so I'm skeptical that this is my client's problem.

My question is, what else could be causing this problem? I appreciate any thoughts anyone might have on this matter.
--Mark

 

[HuskerMark]

Has anyone ever run across error 20500 when using Crystal???
I am really stuck on this one.

 

[kenhamady]

I would do an active DLL comparison on these PC's with your application running, and see if there are differences, and then use a dependency walker to see if you are missing any required DLL files on this PC. It may be that a DLL that is assumed to be existant on each PC is missing or out of date. I described this briefly in my November newsletter which is at:

htp://

http://www.kenhamady.com/news0111.html

Dependency Walker is described at:

http://support.crystaldecisions.com/library/kbase/articles/c2007141.asp

Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB

http://www.kenhamady.com/

tek@kenhamady.com

 

[dips77]

Hi Folks!
This error had been on my nerves a little while back.
Try setting Location of Database(Database Menu bar option)
to "Same as Report"
In my case it has worked fine.
Good Luck