The error usually occurs after clicking on a specific button, but the client says that it has happened when doing other operations too. The problem, though, is that specific button is the equivalent of a "GO" or "Process" button which does a ton of things from creating a sales order, inserting financial transactions etc and finally finishes up by automatically printing out a receipt and kicking open a cash drawer. Not sure if I mentioned that it is a Point Of Sale application. According to the vfp8err.log, the error occurs in a bunch of different places. I've tried cleaning up dangling objects references, contacting the Printer company to see if there is an updated driver, etc. But all my efforts have resulted in no progress in solving this - very frustrating for me, not to mention clients.

I'll give a little more info about the specific form on which the error occurs in hopes that a light bulb will turn on for anyone reading this. I know this is long-winded, but i'm officially out of ideas and really need help.

Although there is a whole bunch of forms, reports and processes that make up the "back office" part of the software, the error occurs only in the Point of Sale form which is run at the cash register - the cashiers only have access to this single form. This form is unique in several ways - first it is designed to run on a touch screen and so the design is a bit different than our normal back office screens - big custom buttons (but all native vfp), larger font (but always Arial), colors etc. This screen also has a bunch of pages - I abandoned the VFP page frame and instead created container classes that are instantiated at runtime on an as-needed basis. The code is pretty tidy even tho there is a lot of swapping in and out of container objects (this is why I thought it might be a dangling obj ref.) I use the Form's AddObject and RemoveObject when a new page is requested by the user...that is, the old container object is removed and the new container object is added. The adding and removing of container objects is handled by a single method, an _assign method of a form property called FormMode...that is, when the user wants to go to the Contact page, the formmode is changed to CONTACT, the _assign method fires which removes the current container obj and adds the Contact container obj.

All works fine, usually, but once in a while the C5 rears it ugly head and I assume that its due to the "not enough memory to complete the operation" error.