turn off db remotely

[Libre]

I have a multi-user db. There are actually 3 computers all on a windows network that access the db, which is located on my hard drive. The computers are in different offices.
I've asked the users to please close the db when they are leaving for the day - so that it does not remain open - and lock me out of design mode. But they sometimes forget and leave the db open.
When I come in in the morning (I'm the first one here) I sometimes have to walk to their offices and close the db manually.
Is there any way to close the app from my computer - so that all instances of the db are closed? Perhaps even a button somewhere with vba code that would do it?

 

[KeithG]

You should have your db broke down into a Front End and a Backend with each user having there own copy of the FE on there computer. Then you can disturbute new FE's when you make desing changes.

 

[MStCyr]

Hello

I would guess that you have a BE/FE configuration. If this is the case, then you can have the database shut down after a certain time of inactivity.

Maurice

 

[Libre]

No, I don't have it split FE/BE.
I've tried that - but run into trouble. DB can't find the tables. I'll work on that one of these days.
Right now, it's all together in one.

 

[TLUK]

Remote shutdown of db

Hi,
I don't claim to be an expert but have a solution that works for me.
The switchboard OnTimer Event refers to a conditional macro called 'shutdown'. The Timer Interval is set to 60000 (60000ms).
Each time the db is opened the switchboard opens a hidden form and the timer triggers the conditional macro to look for a change of value once every minute.
This runs in the background continuously unnoticed on every machine using the db (and does not affect performance).
If I need to close db's remotely I just change the value being checked by the macro from a 0 to 1 (arbitrary values)
Within 1 minute each machine will have looked for the change in value, recognised the change and quit as requested by the conditional macro.
The method does work, not only from work but also from home.
I connect to our intranet from home via a VPN, open the db from home, close the open db's at work using the method described. I usually then copy the db, make changes at home and then send it back rather than make design changes from a distance as it is too slow and unreliable.
Hope this helps
TL

 

[pbaldy]

I've used this, but I agree with previous opinions that the db should be split with a copy of the FE on each user's PC.

http://www.peterssoftware.com/isd.htm

 

[Libre]

Thanks.
Except, I don't have a switchboard.
At least, not the one Access provides - I built my own.
I thought about putting a timer event in it - but started getting bogged down thinking how to determine if there were any active users.
After reading your post, TLUK, I created a Switchboard using the switchboard manager just to take a look at it - but the switchboard I designed has a lot of development in it so I need to keep it. It's just a regular form that the db is set to open on startup.
I know I should split the db to FE/BE, but I can't seem to get around to it. As I said, when I've experimented with it, the FEs can't locate the BE. I know it's my error, and I want to straighten it out when I have the time.

 

[TLUK]

db remote shutdown

Can't you add a timer event to your switchboard? You can add a On Timer event to any regular form created.
I know that a db should be split but have tried to avoid it as it's continually being developed. The db I have built is used in a large school and is used by about 120 staff (typically 10-15 at any one time). There are several buildings and hundreds of PCs.
If it's split and changes are being made regularly how do I redistribute the latest FE to many users in lots of locations?
I have considered using a batch file that would transfer the latest version to whoever is going to use it.
I'm just concerned that this is going to make it more difficult to maintain but I don't think I have a choice.
My db is becoming too unstable and locks once or twice a day when it's very busy. It's easy to fix, but users get annoyed when they have to close it down for a couple of minutes.
I believe that splitting it will reduce the network traffic and make it more stable, particulary as it uses a lot of queries to perform calculations, rather than just storing a lot of data.
Any advice would be appreciated.

 

[pbaldy]

You should definitely split the application. Updating front ends is easy with a batch file, or I wrote a little exe, or there are utilities like this:

http://granite.ab.ca/access/autofe.htm

 

[Libre]

Can't you add a timer event to your switchboard? You can add a On Timer event to any regular form created.

Yes, I can. I'm just not sure how to check for inactivity on the part of the users. I mean, I'm sure I could come up with something - but - I don't really want a timer to shut down the app. I want to do it manually. There may be long periods when the app isn't used legitimately - I don't want it just closing and ticking the user off - especially because it's my boss.

 

[pbaldy]

A solution I've seen used for that is to have a timer running that checks a value in a table periodically. If let's say False, it does nothing. If True, it prompts the user to exit, and can force them out if they don't respond in a timely manner. To get them out, you simply change that value.

Of course, if you split the db you don't have to get them out to make design changes.

 

[GohDiamond]

Here is a thread about remotely shutting down over a network.
Search for : Remote shutdown of a shared DB...

Cheers!
Goh