Software to knock users off

[Guest]

I'm using a program called WhoHasIt to knock users off a front end DB. This
is used to be able to maintain/update the DB. Our particular situation did
not allow for us to push the front end down to users. Users have to use a
shared version on a server.

WhoHasIt does not always work that well with our system. Is there anything
else out there for this problem? Thanks in advance for any reply.

Nick

 

[Roger Carlson]

On my website (www.rogersaccesslibrary.com), is a small Access database
sample called "LogUsersOff.mdb" which illustrates how to do this. It's not
a utility that you can install, but you can incorporate it into your
application.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[Guest]

One question..... Since we all access the same front end, if I set the
table setting to No, how will it know to not log me off and keep me off?

 

[Tony Toews]

I'm using a program called WhoHasIt to knock users off a front end DB. This
is used to be able to maintain/update the DB. Our particular situation did
not allow for us to push the front end down to users. Users have to use a
shared version on a server.

Greatly increased chance of corruption in the FE MDB/MDE if you are
using a shared version. Can you give each user their own copy of the
FE on the server?

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

 

[Roger Carlson]

Well, when I worked in that situation, I ALWAYS worked on a master copy on
my hard drive. That way I could make all my changes, test them and such
without kicking everybody out. Then I didn't need to be in the database
when everyone was kicked out. I only had to kick them out for the few
seconds it took to copy the master copy from my hard drive to the network.

I would suggest you try that. Also, as Tony suggests, see if you can give
them their own copy on the network.

Lastly, if you really MUST kick everyone out while you stay in, the LogOff
sample could be modified to allow you (based on your network login name) to
stay in. I don't have a sample specifically for that, but there is relevant
code in my sample "UserSeesOnlyHisRecords.mdb" which shows how to identify
the user even if you don't have Access Security set.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L