Karen, Thanks for the input. I believe I will run a performance monitor on the memory the EXE is using on the terminal server and see if there are any issues. If there is, it should be fairly easy to match when the form issue appears and the memory level currently being used. However, I am thinking more that it is something to do with locking conflicts in temp files.
Thanks , Bob -- Thompson Technology Consultants LaPorte, IN 46350 219-363-7441 -------------- Original message -------------- From: [EMAIL PROTECTED] I long for the days when you could "zip" to a nothing.exe program to free up memory. I have problems with temp files becoming corrupt and think that doing something like that would fix everything up nicely. I think your app, being hammered on 20 hrs a day, could also use some kind of memory-freeing utility if there was one. I'm assuming you run everything with whileopt off, right? Karen I am having issues on a multiuser application where a user will click an EEP on a form that calls another form and they recieve the message: "Form (Form Name) does not exist" (Form Name) is the name of the requested form. The forms all do exist as users run this app 20 hours per day. This does not happen on just one form, but has been seen on any of the 30+ forms in the app. I can click the Exit EEP and this will close the current form out to the main menu form. I click the Exit EEP on the main menu and the session hangs and must be killed in the task manager. I restart the app (no reboot etc.) and the app runs fine, with no errors. It almost acts as if the network connection has dropped, but this is not the case, and I cannot find out why the session hangs on the last EXIT command. Again, this is intermittent and happens only on occasion. But enough that the users are complaining. (Truthfully, a good app should never have repetitive problems, so I take some personal stake in this) One other oddity is that I have 8 users running this app on a terminal server. One user may see this happen and the others continue running without issue. (Thus I know the network connection has not dropped) With the above scenario, it seems fairly clear that this issue is session related and not machine. I.E. one PC running 8 users on terminal service, one user sees the issue and the others not. I have scanned all the EEPS and there are no DISCONNECT or CONNECT commands that would close the current database and as mentioned, the app runs fine except occasionally this pops up. This is a compiled 7.5 app Any thoughts? Thanks, -Bob --
