Well, here's an update on this situation.

I just got off the phone with this customer. They weren't running a Novell network, so I ruled that option out. We tried rebooting and powercycling and starting our app immediately, but neither of these solved the problem. At that point I had them install the software locally on a client machine and it ran okay. So I had them re-install on the server and after the install it ran okay. I had actually tried re-installing yesterday before I posted my message, but it turned out that one of the diskettes they were using was corrupt. They received a new set of diskettes today, so we tried that as a last resort. Thankfully, it worked.

The only conclusion I can come to is that somehow the app became corrupted? They had been running fine on this current version for several weeks before these problems starting cropping up. I'm not sure what could have caused the corruption, but in any case, it seems to be solved for now.

Thanks for your suggestions and input.

Scott


>>Thanks for your suggestions, George. I think the client said they had an NT network, but I'll ask them again to make sure. I'll also try rebooting and starting our app immediately.
>>
>>BTW, does this error only occur under Novell?
>>
>Scott,
>
>I've only experienced it with Novell because that's what we run. It's obviously something external to the application itself, otherwise it would occur even after a re-boot and it doesn't. In our case, it could be the other software that's running that's causing a problem with the OS. We run a lot of Lotus stuff, and my suspicion is that those programs may be involved. However, that's a WAG.