G
Guest
I have a situation where Access runs a query and spits the results out into
an Excel file which it then opens if the user says he wants to look at it
immediately.
I'm getting an increasing number of calls where users click the appropriate
stuff and get a programmed-in generic error message. In most cases it turns
out they have run the foregoing process, looked at the file, and left it
open. Therefore, the second time they try Access tells them "Hey dummy, you
already have that file AND you have it open!"
Anybody know a way, maybe with FileSystemObject, to test not just for the
existence of a file but whether it is open? If there is one I might be able
to save my users from themselves, but I couldn't find an appropriate method
or property under FileSystemObject.
an Excel file which it then opens if the user says he wants to look at it
immediately.
I'm getting an increasing number of calls where users click the appropriate
stuff and get a programmed-in generic error message. In most cases it turns
out they have run the foregoing process, looked at the file, and left it
open. Therefore, the second time they try Access tells them "Hey dummy, you
already have that file AND you have it open!"
Anybody know a way, maybe with FileSystemObject, to test not just for the
existence of a file but whether it is open? If there is one I might be able
to save my users from themselves, but I couldn't find an appropriate method
or property under FileSystemObject.