Agreed. Networks are finicky beasts...
I used to have a routine for closing/opening files that used FOPEN() and
waits to make sure they're closed first. I'd also have an outer DO loop
for a certain number of tries, then a message so the user can decide
whether to keep trying or go out to lunch. :-)
Ted Roche wrote:
On 10/16/06, John J. Mihaljevic <[EMAIL PROTECTED]> wrote:
Let me look into this a little more closely on my end before anyone else
wracks their brains over it.
Timing issues, as Chet indicated: one network may be slower than the
other, or different OS and network clients are caching that the file
is in use when an attempt is made to delete it. Possible work-arounds:
attempt to open the file exclusively with an FOPEN() to clear the old
locks, or add a small timeout (INKEY(.5) or WAIT 0.5 or Win32API
Sleep) to give the networking client and server a chance to clear the
status of the now-closed file.
_______________________________________________
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
** 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.
