On exclusive open for write

[vezerid]

I have identified the relevant threads and have read the pages in the
microsoft support website. Experts, please share with me:

From reading the code I understand that the procedure is not

full-proof.

A function IsFileOpen attempts to open a file for I/O. It then closes
it and returns TRUE if an error was produced while attempting to open.

Then, the attempt to open at Excel-level is done through invocation of
IsFileOpen in an IF.

In other words, broadly speaking, we have the following sequence of
events:

Open at I/O level.
Close at I/O level.
Workbook.Open

Thus, it is possible that between the Close and Workbook.Open someone
else has opened the file. Am I correct? Am I missing something?

Is there a full-proof way to open a file exclusively for write and then
use object libraries with it?

Regards,
Kostis Vezerides

 

[Tim Williams]

Why don't you just try to open the file: if you can open it then why close
it again?
Just open it and keep it open, or raise an error if the file can't be
opened.

Tim

 

[vezerid]

It is because I want the file to work for multi-user access. The idea
is that SPR1.xls is used as a template for data entry by many users. By
clicking a button I want the elements of the form to be stored in a
central table, in SPR2.xls, located in the network. Therefore locking
issues are important.

Kostis

 

[Tim Williams]

That still doesn't explain why, if you want to write data to the file, you
don't just try to open it and then keep it open if you succeed.
I don't get why you open it and then immediately close it (only to open it
again later).