Yet another thing to look into: drive mapping.
Also compare the path statements between the working machine and the machine that locks up. A 'set' command from a DOS box will show it. Or the temp directory location. Does the user have the same rights on each machine, does it behave the same if an administrator level user is logged in. That's about all I know. J Hans From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: Monday, September 12, 2011 2:57 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Off Topic Network issue I know, sometimes I wish this user had never bought my app. Marc From: Dan Goldberg <mailto:[email protected]> Sent: Monday, September 12, 2011 2:21 PM To: RBASE-L Mailing List <mailto:[email protected]> Subject: [RBASE-L] - Re: Off Topic Network issue I think I have seen this post for at least the last year or so. Maybe it would be cheaper to have RBTI come by and fix you up!! Dan Goldberg From: MDRD <mailto:[email protected]> Sent: Monday, September 12, 2011 12:06 PM To: RBASE-L Mailing List <mailto:[email protected]> Subject: [RBASE-L] - Off Topic Network issue I have an office with a dedicated file server, and 2 workstations. They can run my app on either workstation fine but when the second workstation connects at the same time it slows to a crawl. They do not have RBase running on the server. This is that same nutty office where 1 workstation locks up at 5:00 or so, or I should say RBase locks up. I know it is not a problem with RBase but it really gets me when they RBase locks up, well duhh that is the only program you are running at 5:00, and that is the only program they run 99% of the time. So, of course any hardware problem is only going to affect what is running. Their computer tech is going to call me and I was wondering if there is anything I can suggest? Thanks Marc
