There is a WRITESEQF that does exactly that. It makes sure the data is actually written to disk and not just buffered before continuing with the next UniBasic command in the program.
Gordon J. Glorfield Sr. Applications Developer MAMSI (A UnitedHealth Company) 301-360-8839 [EMAIL PROTECTED] wrote on 11/01/2005 08:56:05 AM: > Havent I read about a WRITEF, that forces flushing? > On 11/1/05, David Jordan <[EMAIL PROTECTED]> wrote: > > If you are talking about using the sleep statement, I assume you are using > > the same program to write and read. I believe that the write process does > > not return to the program until it has successfully completed the write. > > > > However if you are dealing with large type 1 files consider using the > > Openseq, Readseq, writeseq facilities as these are effective in dealing with > > very large records. Readseq is a lot faster than using REC<n>. > > > > Regards > > > > David Jordan > > Managing Consultant [SNIP] This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
