Larry, I wish I could but the part of the code I was looking at was where one line copies a file to a network mapped drive and then the next line of code deleted the file from the local directory.. Believe it or not sometimes (maybe 2 out of 100 times) the delete on the local drive would occur before the file got written to the Mapped drive, so on a few instances the file never makes it to the mapped drive. Trust me I have looked at everything, including making sure a virus scan is not being done, connection speed, etc. It should not happen, but somehow does, I am not sure where the issue comes from (Rbase, Microsoft ?). By my simply adding a pause for 1, the problem went away completely. Also in the same code, I have the program printing to a pdf file, copying the output to a mapped network drive, then deleting it on the local drive.. I have to put a pause for 2 between the print command and the copy command because sometimes the pdf would not be there when it hit the copy command, even though obviously the print command had completed. So the Pause for N commands have to stay to make sure the files are actually there.
-- Frank -- Frank Taylor, Systems Network Administrator -- F.J. O'Hara Corp, Boston, MA -- [EMAIL PROTECTED] - 617-790-3093 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Lawrence Lustig Sent: Friday, February 25, 2005 1:52 PM To: RBG7-L Mailing List Subject: [RBG7-L] - Re: Pause & Pause For Behavior > Suggestions welcome. Remove the PAUSE 2. Once you write stuff to the operating system, it will correctly make sure it gets written to disk. You don't need to "give the hard drive enough time to make sure the file is fully written". -- Larry
