I do a lot of work in MS Word for one client, and I use FileMaker 7 to manage and check the complex web of files she sends me.

My problem is that FileMaker infrequently (every 25 minutes) crashes with a "buffer overrun C++ runtime error" message while I'm working in MS Word (2000).

I have no idea what this error denotes (i.e. a problem with Word, Windows, FileMaker, or some combination), but it's only FileMaker that crashes, and it's only while I'm in Word. On restart FileMaker works fine for a while again. There does not appear to be a trigger (perhaps a simple "find" request, but not always).

Has anyone seen this? I can find no posts on it (somebody had a vaguely similar problem in photoshop.)

Here are some potentially influencing factors: I run huge complex macros in both Word and same for FileMaker (i.e. scripts automatically create citations for 100s of references in Word and the convert them to Excel for auto checking--it's a highly technical textbook, by the way).

The crashing happened slightly more frequently before I update to SP2 (Windows); it happened also with FM5 (my previous version).

I use many container fields with embedded shortcuts to the files as stored on my hard drive.

Any theories would be appreciated.

Every 25 minutes? Any process running kicking in every 25 minutes? You'll have to try and narrow it down to the exact circumstance that triggers the crash. IOW, try to make it happen at will.

I don't recall seeing too many mentions of a crash like this on this list or any others. I had a couple of those in the FM7 beta program when I was using FM's ActiveX objects (calling FM from the outside). Are you doing any of that?

Try this: Start | Control Panel | System | Advanced | Performance | Advanced | Memory Usage | System Cache (instead of Programs)

Thanks, people.

I think the process that's causing the trouble is my Outlook e-mail checking now, but I'm not sure.

But I'm curious, transpower, what is the reason that "programs" is the default memory usage, if "System cache" would work better.

I'm afraid I probably won't know whether it works until the weekend, when I have another batch of files to process, but thanks for the suggestions,

Ian

Ian:

It's based solely on my experience with working with numerous XP computers. Apparently (and this isn't based on anything from Microsoft) there is a timing problem involved in writing the cache for computers with large amounts of RAM; writing the cache with minimum delay appears to solve this problem and actually improves performance, which seems to be counter-intuitive. Anyway, it's worth a try for your situation.

I know this is an old post but I've been getting this error when I am importing Outlook email using POP3IT plugin) and I think you mentioned something about Outlook/Windows in your email.

Is this problem still happening to you?

I debugged and it happened when I was inserting a large PDF file into a container file.

Any advise is welcomed.

I've finally licked this problem (It's only taken about two years).

The buffer overrun only happens when my cursor is left in a container field. That factor is the key trigger. I use literally hundreds of macros and scripts toggling between MS Word, Excel and FMPro. (This crashing only happens on a PC, by the way -- as I use both Macs and PCs).

My solution is that whenever I run a script that uses one of my container fields, I end it with "Go to field []" (i.e., with no field specified) so that my cursor is never left in a container field.

I started adding this to all my scripts about 6 months ago, and I encountered my first "buffer overrun" in six months today. I quickly scanned the related script and noticed that the "Go to field []" script step was not added to that one script.

So I'm fairly confident I've nailed down the solution, even if I don't know exactly why leaving my cursor in a container field creates such bugs.