I don't really have any choice. The network is connected using a T1 and has never been prone to any problems. As I mentioned this application has been running this way for about 8 years at 20 sites from Florida to Hawaii (Hawaii and Florida have very slow connection speeds) and this is the first time I have seen it. It is also consistently failing at the same place.
All other table reads and writes in the application at this location work fine. The only thing different about this is that it is in a class and is failing in a .Closetables() procedure. There are other classes down the line that do the same thing and aren't failing. Jeff Jeff Johnson [EMAIL PROTECTED] SanDC, Inc. 623-582-0323 Fax 623-869-0675 Alan Bourke wrote: > Jeff Johnson wrote: >> Can you go into a little more detail of what you mean by your message below? >> > > Well, I'd never open a table directly over a connection as slow and > prone to disconnects as an WAN connection over the internet. I wouldn't > even do it over a wireless network inside an office. I would always get > the users to run the application via terminal services sessions or similar. > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
