I just spent way too much time testing.  I hope my table is 
understandable.

CONDITION                   SAFETY OFF - CATCH MESSAGE   SAFETY ON - 
CATCH MESSAGE

Closed file exists          None (file is overwritten)   Messbox only

Target directory read only  Cannot create file           Cannot create 
file

File open via FOPEN()local  File is in use               File is in use

File open via FOPEN()remote Cannot create file           Messbox if O - 
Cannot create file

File open via Notepad       None (file is overwritten)   Messbox only

File open via Word          Cannot create file           Messbox if O - 
Cannot create file

File copy in progress       Cannot create file           Messbox if O - 
Cannot create file


These tests were done from two workstations.  One ran the code and the 
other controlled the status of the file.  The FOPEN() local is an 
exception as that was done in the machine running the code. I used the 
unbuffered read/write option on FOPEN() for the results recorded here.  
The default read/only appeared to match the Notepad results. 

Joe Yoder

>>Based on my experience with trying to trap errors from a Copy File To
>>command, I'm guessing that one copy would succeed and the other user
>>would get the Interactive Message Window that states that the file
>>already exists and asks what to do.  Only the operating system on the
>>server knows which of the two simultanious copy commands got it's
>>attention first.
>
>Date: Tue, 03 Jul 2007 22:27:27 -0400
>From: Ken Dibble
>To: [EMAIL PROTECTED]
>Subject: re: Simultaneous Copying??
>
>Thanks, Joe.
>
>Since my app runs with SET SAFETY OFF, the user wouldn't see such a message
>and COPY FILE would merrily overwrite the first-laid-down bits with the
>second user's copy while still writing the last of the first user's copy?
>
>Doesn't copying a flat file imply a lock on that file until the copying is
>done? Or am I completely misunderstanding how this works?
>
>Thanks.
>
>Ken
>www.stic-cil.org
>
>
[excessive quoting removed by server]

_______________________________________________
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.

Reply via email to