Bob,
I think you may be incorrectly discounting network issues. If there is a flaky NIC, the connection may lost momentarily - long enough for your app to get hosed for the one user. If an R:BASE session is trying to retrieve data (e.g. from SYS_FORMS3) at the moment that the interruption occurs, but the other users are not interacting with the database at that moment, then only the one user would be impacted. I'd suggest changing out the NIC(s) in the terminal server and see if it fixes the problem. Emmitt Dove Manager, DairyPak Business Systems Evergreen Packaging, Inc. [EMAIL PROTECTED] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [EMAIL PROTECTED] From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, November 25, 2008 8:33 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Form does not exist 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 -- Thompson Technology Consultants LaPorte, IN 46350 219-363-7441
