Database Lock

[Gee]

I have and '03 Database on a server with the Back End in a folder on the same
server.

My problem is that the "Lock" will not always disengage. I go in to make
changes in the forms and it tells me that it is locked because someone is
using it, but they're not. I disabled the upper right "x" to close the
database so they could only use an Exit button, but that didn't work.

What can I do to fix this? The big guys are getting tired of having to go
in and clear it so I can work on it.

Thank you in advance for any help.
G

 

[John W. Vinson]

I have and '03 Database on a server with the Back End in a folder on the same
server.

My problem is that the "Lock" will not always disengage. I go in to make
changes in the forms and it tells me that it is locked because someone is
using it, but they're not. I disabled the upper right "x" to close the
database so they could only use an Exit button, but that didn't work.

What can I do to fix this? The big guys are getting tired of having to go
in and clear it so I can work on it.

Thank you in advance for any help.
G

If you're using a single shared frontend linked to a shared backend, you're
getting the WORST combination: all the problems of a shared database (such as
the locking you see) with none of the benefits!

If you do need to put the frontend on the server, at least give each user
their own private copy in their own private folder.

 

[Arvin Meyer MVP]

1. Do you have Compact On Close turned on? If there's an error, it may stop
your closing.

2. Do you have a Boolean control with code like:

If Me.chkWhatever Then

There is a bug in VBA that can hang Access. Change your code to:

If Me.chkWhatever = True Then

3. Do you have any recordsets that haven't been explicitly closed? Make sure
that your exit routine closes all the objects that you open (as opposed to
object used by the application)

 

[aaron.kempf]

there are no benefits to a shared Jet database.

all there is involves:
corruption
bad performance
mountains of vba code (that won't run anywhere else)

the alternative.. is a simple client-server database.. that is
designed -- from the ground up-- to support multiple users.

you don't need 3 tiers of Jet.
You need to upsize to SQL Server.

-Aaron

 

[aaron.kempf]

Arvin;

So sorry that your database access library makes you explicitly close
all your variables.

This is a horrible horrible Jet bug and most people-- when they see
something like this-- they move to a real platform like SQL Server

-Aaron

 

[Arvin Meyer MVP]

So sorry that SQL-Server doesn't have a front-end. FWIW, the bugs occur in
VBA not Access and do so no matter whether the data engine is either Jet or
SQL-Server.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


Arvin;

So sorry that your database access library makes you explicitly close
all your variables.

This is a horrible horrible Jet bug and most people-- when they see
something like this-- they move to a real platform like SQL Server

-Aaron

 

[aaron.kempf]

SQL Server has a frontend.

It is called 'access data projects'.
or 'Reporting Services'.

-Aaron

 

[aaron.kempf]

and sorry the bugs occur _WHERE_?

I don't have to de-instantiate my ADO recordsets, why do you put up
with a DAL that gives memory leaks?

-Aaron

 

[Gee]

Wow, lots of discussion but I really didn't get an answer that I can
understand.

What do I need to do to make the break when the program is closed?

I can't be the only one facing this problem.

Help?

Thanks,
Gee

 

[John W. Vinson]

I have and '03 Database on a server with the Back End in a folder on the same
server.

That's your problem.

If you have all the users sharing the same frontend you will constantly have
locking issues.

Give each user their own copy of the database, on their own machine
(preferably), or in their own private folder on the server if that's
necessary.

 

[Arvin Meyer MVP]

Wow, lots of discussion but I really didn't get an answer that I can
understand.

What do I need to do to make the break when the program is closed?

I can't be the only one facing this problem.

Help?

Actually, you did get an answer, from John Vinson:

You need to put a copy of the front-end on EACH user's workstation. Sharing
a front-end is an inevitable recipe for problems.

 

[Gee]

Ah, I see...now I understand.
They like to make changes to the front end quite often. I'd have to update
each copy.
I think we'll just have to live with this and do the unlock like we've been
doing.

Thank you for your answers.
Gee

 

[Tony Toews [MVP]]

They like to make changes to the front end quite often. I'd have to update
each copy.
I think we'll just have to live with this and do the unlock like we've been
doing.

I specifically created the Auto FE Updater utility so that I could make changes to
the FE MDE as often as I wanted and be quite confident that the next time someone
went to run the app that it would pull in the latest version. For more info on the
errors or the Auto FE Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the FE on each PC up
to date.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[aaron.kempf]

in other words-- you make your end users wait 30 seconds so that you
can enum all your temp tables, your queries-- and three tiers of Jet--
and refresh all your linked tables

what a joke

do you really get paid for what you do Tony? Or do you just work for
blowjobs?
you have got to be the worst software architect I've ever heard of in
my whole life

 

[Tony Toews [MVP]]

in other words-- you make your end users wait 30 seconds so that you
can enum all your temp tables, your queries-- and three tiers of Jet--
and refresh all your linked tables

No, that's not how the Auto FE Updater works. Other then opening the FE MDB/MDE on
the server to determine the version it does nothing with the FE MDB/MDE.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[aaron.kempf]

**** you tony

you're LYING

No, that's not how the Auto FE Updater works.  Other then opening the FE MDB/MDE on
the server to determine the version it does nothing with the FE MDB/MDE.  

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 athttp://www.granite.ab.ca/accsmstr.htm
   Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/

 

[aaron.kempf]

you enumerate all your queries, copy them over if there is a
difference, etc--

what a waste.. you've got to be the worst programmer I've ever heard
of in my whole life, you don't understand anything about architecture.

and you sit there and insist that people use THREE_TIERS_OF_JET

and why?

JUST BECAUSE YOU ATTEMPTED _ONE_ UPSIZING AND YOU FAILED-- you take
your egocentrism and mandate that everyone else does it just like you

**** you and your AUTO FE UPDATER

keep your tables and queries where they belong-- SQL Server!
keep your tables and queries where they belong-- SQL Server!
keep your tables and queries where they belong-- SQL Server!
keep your tables and queries where they belong-- SQL Server!
keep your tables and queries where they belong-- SQL Server!

 

[Tony Toews [MVP]]

No, that's not how the Auto FE Updater works.  Other then opening the FE MDB/MDE on
the server to determine the version it does nothing with the FE MDB/MDE.  

[/QUOTE]

f*** you tony

you're LYING

I'm lying about a utility I wrote?

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

you enumerate all your queries, copy them over if there is a
difference, etc--

No, the Auto FE Updater copies across the entire FE file without touching it other
than determining the version of the FE MDB/ACCDB/MDE/ACCDE.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

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

oh, so it's the file copy process.. so you make your end users copy
over a 50mb frontend..

and a new blank tempdb..

and anyone that builds custom queries-- gets them overwritten (without
notificiation)

sounds great, tony!

-Aaron