Hi all,
Problem: there is a database in use at my work that is not a FE/BE db that occasionaly needs updating, used to be ok to do by bringing up a list of users and contacting them to close the DB. Problem is the DB is now being accessed through a wireless network also, when users of the DB on the wireless access close at times it doesn't clear the connection to the DB so access thinks the DB is still in use. The only way to clear this at the moment is to down the server and delete the locking file on the server then restart or wait till the next day and delete the locking file before anyone accesses the db that day.
Is there a way to change the information in the locking file so it looks like the connection has been cleared thus allowing you to open the db then close it again to get rid of the locking file?
Any ideas appreciated.
Thanks .
Problem: there is a database in use at my work that is not a FE/BE db that occasionaly needs updating, used to be ok to do by bringing up a list of users and contacting them to close the DB. Problem is the DB is now being accessed through a wireless network also, when users of the DB on the wireless access close at times it doesn't clear the connection to the DB so access thinks the DB is still in use. The only way to clear this at the moment is to down the server and delete the locking file on the server then restart or wait till the next day and delete the locking file before anyone accesses the db that day.
Is there a way to change the information in the locking file so it looks like the connection has been cleared thus allowing you to open the db then close it again to get rid of the locking file?
Any ideas appreciated.
Thanks .
Last edited: