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 06 JUN 2007 12:07:09PM Simon G Wilmot wrote:

Hi all,

Bit of a daft question this, as I know there are ways around it, but is there a way to directly lock an Operating System record when in OI ??

TIA,

Simon


At 06 JUN 2007 05:46PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

OSOpen should do it.

The Sprezzatura Group

World leaders in all things RevSoft


At 07 JUN 2007 04:51AM Simon G Wilmot wrote:

That was what I had hoped.

I tried that on two different machines to test that and it didn't appear to work (using UD3)… ie the second one opened the file already opened by the first.

Simon


At 07 JUN 2007 11:32AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

In which case you may need to use some lower level Windows API calls to accomplish this.

Note that the LH Network driver has nothing to do with the "OS"-functions - they are direct calls to Windows.

The Sprezzatura Group

World leaders in all things RevSoft


At 08 JUN 2007 04:12AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Alternatively, if you are only accessing this file from within your OI app, and that's the only place you care about the lock, then just lock a consistent handle.

lock @FILE_SYSENV, dosFileName then…..

The Sprezzatura Group

World leaders in all things RevSoft

Revelation Conference 2007, London - Wednesday 27th June Click here to register for the premier Revelation Software EMEA event of 2007


At 08 JUN 2007 04:25AM Simon G Wilmot wrote:

Thats the workaround I was going to use, just it would have been nice to do a good clean lock … :-)

Simon

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/162820d7a241b699852572f200588bc9.txt
  • Last modified: 2023/12/28 07:39
  • by 127.0.0.1