Remote Closing of Forms or DB

[Guest]

Is it possible to close an open form or database from a remote location for
maintenance?

There are some instances where I may need to do some work to the database as
a whole and need people to log out of the program. Management personnel seem
to be the worst at leaving the program running when they go home for the day.

Also, could I incorporate a timer function that would allow users to receive
a small pop-up with a timer "System Going Down in XX:XX:XX. Please log off."

 

[Guest]

Yes you can. the basic concept is

1. create a hidden form that uses a timer event to routinely check a boolean
value in a table. If it is set to false nothing happens... However when you
change the value to true then it will log the users out and not allow them
backin until you reset the value.

Their is an example at
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='ForceUserOut.zip'

Daniel

 

[aaron.kempf]

dude you're a ****ing retard

don't use mdb for anything
use adp

you can KILL 57 in order to force someone out of an ADP

MDB is for ****ing newbies and losers; i mean seriously here

you shouldn't need to close out jack shit in order to take a backup


unnecessary complexity is not necessary

 

[Joseph Meehan]

dude you're a ****ing retard

don't use mdb for anything
use adp

you can KILL 57 in order to force someone out of an ADP

MDB is for ****ing newbies and losers; i mean seriously here

you shouldn't need to close out jack shit in order to take a backup


unnecessary complexity is not necessary

I beginning to think that Aaron may have lost his job due to his
inability to properly program Access and that is why he has such hate for
it.

 

[Tony Toews [MVP]]

Is it possible to close an open form or database from a remote location for
maintenance?

There are some instances where I may need to do some work to the database as
a whole and need people to log out of the program. Management personnel seem
to be the worst at leaving the program running when they go home for the day.

Also, could I incorporate a timer function that would allow users to receive
a small pop-up with a timer "System Going Down in XX:XX:XX. Please log off."

Yes, you could do that but I wouldn't bother. A half hour of
inactivity and kick them out.

HOW TO: Detect User Idle Time or Inactivity in Access 2000 (Q210297)
http://support.microsoft.com/?kbid=210297
ACC: How to Detect User Idle Time or Inactivity (Q128814)
http://support.microsoft.com/?kbid=128814

However we found that the code which runs on the timer event must be
disabled for the programmers. Otherwise weird things start happening
when you're editing code.

Also print preview would sometimes not allow the users to run a menu
item to export the report to Excel or others. So you had to right
click on the Previewed report to get some type of internal focus back
on the report so they could then export it. This was also helped by
extending the timer to five minutes.

The downside to extending the timer to five minutes was if a person
stays in the same form and at the same control for considerable parts
of the day, ie someone doing the same inquiries, the routine didn't
realize that they had actually done something. I'll be putting in
some logic sometime to reset this timer whenever they do something in
the program.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[aaron.kempf]

that is just hilarious

a proper database can be backed up while people are using it LoL

MDB was obsolete a decade ago; and it still is

-Aaron

 

[Joseph Meehan]

that is just hilarious

a proper database can be backed up while people are using it LoL

MDB was obsolete a decade ago; and it still is

-Aaron

For my professional applications, they were always backed up, even with
people using them.

 

[aaron.kempf]

I think that you're full of crap dude

If backing up a database was so simple then why is this NooB so
worried about making an application smart enough to shut itself down?

So that he can change a table on the backend?

I still don't have trouble with that.

MDB was _NEVER_ designed to work for multiple users.

with _FREEWARE_ SQL Server; Access Data Projects RUN CIRCLES AROUND
YOUR MDB _CRAP_

you're stuck in the 90s, kid

-Aaron

 

[aaron.kempf]

does MDB even support distributed transactions?

does it have a built-in scheduler?

SQL Server, MSDE; free-- out of the box-- come with a 'maintenance
plan wizard' that automates taking a backup... it works SWEET for most
situations.. and the bottom line is that SQL Server has remote
adminstration tools.

MDB you can't run in across a VPN; or across a wireless network.

SQL Server has more advanced replication; disconnected edits, to
support the travelling salesman for example-- that MDB can't even
dream of.

MDB is for babies and retards; lose the training wheels you _WUSS_

-Aaron

 

[aaron.kempf]

and you can't call yourself a professional

you're a ****ing hack

you use _ACCESS_MDB_?

_AS_IF_

you need to go to school and learn how to calculate ROI, dude.. your
MDB crap has _NO_ roi, SQL Server is easier / better development.

you're just too ****ing stupid to learn a real database.

We will beat you in the open market, kid.. SQL Server runs circles
around MDB; and it's the same price.

-Aaron