Brandon --

OK, am glad that your classloc problem has been resolved ... but wish I knew how to resolve it as well.

So, some questions remain from before, in trying to isolate your bonk:

Does it happen when it's the first thing you do after opening your VFP session?

Does it happen to all SCXs?

When it happens, is there any other information other than "buffer overrun"? (I have no idea what that is -- never heard of it)

Jim

>I followed my class hiearchy all the way up and indeed found an error in the classloc value at the top level class. It still referenced a relative location that was no longer valid. VFP never failed on this - evidently if the classloc fails, it searches the defined path for the class. I fixed the classloc and now the warning error messages are gone. Unfortunately, the fatal bonk is still there! At this point it appears the 2 issues may have been unrelated.