Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 20 JAN 2000 01:40:16PM Wayne Shepard wrote:

OSCLOSE does not unlock the file and update the directory header. It appears to merely set a flag somewhere that says "It's okay to close the file when it is convenient." Is there any way to force the system to actually close the file?

My application is writing a file and then using DDE to cause another session to open the file and process it. But because the file is not closed, I'm getting "file locked" errors. Perhaps there is a convenient work-around for this?


At 20 JAN 2000 02:28PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

What OS are you running on?

You could try using the flush() statement after your OSClose.

The Sprezzatura Group

World Leaders in all things RevSoft


At 20 JAN 2000 08:13PM Wayne Shepard wrote:

Hooray! It worked!

For the record, I'm using the OI 3.7 Evaluation Demo.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/0491bcb708578b838525686c0066908a.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1