Hi David,

>Thanks for reply. I < think > I have ruled out a double launch of the app. However I am wondering about shared .DLL's and *Window's Stuff*.

What's happening is that somehow the instance handle is being released. That's the meaning of the error. My explanation was based on my encounters with that error. In your case, the first place I'd look is the ON SHUTDOWN... program. Perhaps something in there is doing it, but I can't imagine what it could be.

>Also, any chance might be related to overrunning temp files. I noticed lots of tmps due to a bunch of new client pc's without a c:\temp path.

I really don't know, but I know how I'd make sure it wasn't. While it's not documented, you can control both drive and directory for the tmp files, in CONFIG.FPW. What I did in Win 3.1 was to write out a batch when the application started up, and deleted it upon normal termination. The AUTOEXEC.BAT file looked for this batch file and executed it and deleted it after running. The batch deleted any tmp files it found in the directory where the tmp files were store (not the Window's temp directory) and then ran CHKDSK.

It's very much like proving an algorithm. Once it's proved, if problems arise you know where the problem isn't. It doesn't necessarily mean that there isn't a programmatic problem (such as a possible need for stronger data validation), but you've eliminated a possible source.

>PS - have a local customer buys lots of carpet from you guys!

I hope he buys lots and drives the stock price up.:-)