PDA

View Full Version : Check In-Use Function



NewsArchive
02-01-2012, 01:46 AM
SB 7.6
If I do a Check In-Use on a file and it IS in-use, is there any way,
thru SB, to make it NOT in-use so I can delete it?


--
Darrel (Dee) Witham
Professional Data Services, Inc

NewsArchive
02-01-2012, 01:46 AM
Hi Darrel,

> SB 7.6
> If I do a Check In-Use on a file and it IS in-use, is there any way,
> thru SB, to make it NOT in-use so I can delete it?

It depends on different factors. But if an .exe is in-use and "locks"
different .dll dependencies, then you can try to terminate the .exe. The
"Terminate Active Application..." can handle this. But be careful when
ending a process and the "Gently Close Application" option is not use (and
you "kill" the process). In this case if you end an application, you will
lose unsaved data. If you end a system service, some part of the system may
not function properly.

Then there are active (running) Services. If a Service is active and
"locks" files, you have to stop the service. This will unlock the service
file including dependencies. Then you can replace the file(s) and restart
the service (see "Check Service..." and "Edit Service..." script functions).

Does this help?

Friedrich

NewsArchive
02-02-2012, 12:33 AM
It does and it doesn't - the file being locked is a Pervasive Btrieve
log file. I stop the Pervasive engine, do a few things and then restart
the Pervasive engine. If I have a Pervasive update to perform, I run
the Pervasive install and that is where it states that the .log file is
being used exclusivly - close all applications and retry or cancel. If
I cancel my SetupBuilder install and select retry - the Pervasive
install goes on its merry way. I cannot see why my SetupBuilder install
would have that file locked. I am also talking with Pervasive about
this.

Dee

NewsArchive
02-02-2012, 12:37 AM
Hi Darrel,

SetupBuilder itself does not "lock" your .log file. If you do a "Check
In-use File..." on that .log then the installer checks if write access is
possible. If this is not the case, it returns 1, which means the file is in
use.

Perhaps the process that "locks" that .log file needs some time to terminate
and free resources?

Friedrich