Application Error involving ref'd memory

[bondhedger]

Help Please! During both development and (attempts) to run VB apps and VBA apps (excel) I have been getting many errors involving "referenced memory", both on the "read" and "written to" sides. A typical error message will be:
"Application Error-- The instruction at "0x60006599" referenced memory at "0x004035d0". The memory could not be "written". I am given the choice to blow out of VBE or Excel (during development) or the App (if I'm running it) OR I can debug which throws me into visual C++ and a bunch of assembly code. The error from the debugger there is along the lines of "Unhandled exception...(FM20.DLL): 0xC0000005: Access Violation." This memory related error surfaces (I think ONLY) with apps and spreadsheets where I am calling to an outside vendor's API. I'm kind of wondering if this is some wierd attempt on the vendor's part to keep me/others from channeling data to non-paying users. This is absolutely not what I'm up to, nor am i capable. Any thoughts and help would be wildly appreciated. Thx in advance.

[JoshT]

I've just had a similar problem in an Access 2000 VBA form. I fixed it by changing the code around and re-compiling. It could be the way objects are being loaded and unloaded into memory.

Other guesses?:
A corrupt dll somewhere
Malfunctioning physical memory.

Have you gotten the message with other use of the computer. I get it occassionally when browsing folders with explorer or opening outlook express.

Josh

[bondhedger]

Yeah, now that you bring it up, windows explorer and ms0utlook have generated similar "ref" errors. I've had a few "unnatural occurences" since switching to win2000pro and office2000. I've got one app that i finished at work today that i just sent home. i want to see if it crashes royally there too running the same O/S and VS6ent. After your comments, corrupt dll or some kind of microsoft office based memory sequestering is the culprit. I'm not far enough up the programming curve to know what it is. So, i'm gonna solve for what it isn't, first. I'll let you know what happens and THANKS for the ideas.