Users in database

[Naz]

Hello

I have a database that is published as a runtime to our department, the
runtime access the FE and the BE sits elsewhere.
I want to update the FE but it won't let me make any changes because it says
someone is in the database, both FE and BE show that small record locking
file. I've asked all users of the database to come out and they have but
nothing....i ran the ShowCurrentUsersRoster from the MS website but that
didn't show the user name of the person the DB think is using it just shows
termm1.

Is there anyway you can reset or boot users out?


Thanks

 

[Daniel Pineault]

Take a look at

http://www.rogersaccesslibrary.com/download3.asp?SampleName=LogUsersOff.mdb

it should be exactly what you are looking for
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.

 

[a a r o n . k e m p f]

if you used SQL Server-- and ADP-- instead of a depecrated format
(MDB) then you'd be able to just run a SQL stored procedure

exec sp_who2


If your database doesn't fit your needs, move to SQL Server

 

[Aaron Kempf knows nothing]

(MDB)

 

[Arvin Meyer [MVP]]

Is there anyway you can reset or boot users out?

Here's the code:

http://www.datastrat.com/Code/KickEmOff.txt

Here's a demo of the code:

http://www.datastrat.com/Download/KickEm.zip

 

[Arvin Meyer [MVP]]

It's pointless to continue, so this will be my last post.

You've never had to distribute to those without Access or you would quickly
see where a runtime is important. That's especially true where Access is a
front-end within a shrink-wrapped software package. There are millions of
those in use right now.

ADP does not necessarily work better. For the most part it works the same.
There are a few bugs which were never corrected by service packs, like a
lookup then trying to check a checkbox which caused an immediate crash in
version 2002 ADPs. I don't know if that happens in 2003 because I rewrote
the app as an MDB to avoid the problem.

We've never once, in many thousands of deployments had a hassle of any kind,
except with an Oracle database over a dozen years ago.

My databases open quickly, even when lots of code is running. So either you
have underpowered machines, or you don't have any code in your forms. There
is no 2 second wait on anything, including large queries. The difference is
understanding how to build a database using proper indexing and RI.

I have never had any corruption in any database I've worked on or
administered in over 5 years. In fact the last database that I had to fix
was a SQL-Server 2000 database which was severely corrupted. I also haven't
had any problems caused by SQL-Injection or the Slammer worm which is unique
to SQL-Server.

There is no 1 perfect solution to anything. JET has its place, so does
FoxPro, and SQL-Server. One size does not fit all, and never has.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

message
im sorry, a runtime can't be created by my beloved ADP?
i've never had a probelm with that

ADP just works better-- YES he should change to a better engine-- so
that he doens't have to deal with corruption and linking hassles.

deployment hassles--

LIFE IS JUST MUCH SIMPLER WHEN YOU KEEP IT ALL WHERE IT BELONGS.. THAT
MEANS ON THE DATABASE SERVER

so do you LIKE makign your customers wait an extra 2 seconds when you
open the app.. so that they can sync the queries from the other
frontend?

FOUR TIERS OF JET IS MORE COMPLEX THAN WHAT ANYONE NEEDS