Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MS Access 2K

Status
Not open for further replies.

cg084

Technical User
May 3, 2002
67
GB
Hello,

I have an Access 2k database running on a windows NT operating system. On a fairly frequently cycle this database stops all users from entering any new data to the database. This also stops the main table from being viewed and all design changes. I have checked the record locking options and this is set to Shared with Edited record lock and Open databases using record level locking selected.

It is confused me as to what is occuring with the database. Yet when everyone finishes with the database after a while it becomes workable again.

Very difficult to see the problem.

Hope someone can help.

Cheers CG084
 
Hi

When you 'stops' these things from happening, what actually happens Error messages for example?

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now - UK
 
Have you perhaps set your AntiVirus program to scan in such a time cycle?
MakeItSo
 
Hello,

Database had been working fine yesterday then today the same problem appears. There is an error message and it is.

"Could not update; currently locked."


This error message to my knowledge only appears when a new record is created and a value in a combo box is edited. It could be any combo box that causes this.

By the time i get in to the database to investigate further. The problem can take about 10 minutes and it resolves it self.

Very hard to track the problem.
Hope someone can help.
Cheers CG084.
 
It defintiely sounds like some kind of scheduled job running to me.

Antivirus scans or backup jobs running seems the most likely.

I'm almost certain it isn't a problem with MS Access or your database.....

Ed Metcalfe.

Please do not feed the trolls.....
 
If it was record locking I don't think it would affect design changes (or entering new records)......

Ed.

Please do not feed the trolls.....
 
Hello,

Really is quite annoying problem this. Everytime it freezes and it does appear to do that. You select a value from the Combo box It pauses for a while then gives you the error message. However if you enter text in to one of the text boxes it will hapily accept the change. If it is some kind of shceduling would that be from the server. If so there are other databases that appear to operate OK. Biggest puzzle for me and it would be nice to know why.


Next time the db throws one i will attempt to look at all tables and forms to see if it is only the one table in the db causing the problem. So i will let you know.

In the meantime if any one may have any suggestions and ideas please let me know.

I appreciate all of your feedback.

Cheers CG084
 
Hello,

This is still causeing a problem. So far this database has locked down twice now. I checked to see which tables were affected by the locking this proved to be very difficult. Upon looking at the design of the database the main table form has a combo box looking at values in table 3. While the Main table table has the same field as a combo box but it uses table 2 for its value. This is the only thing i can see that conflicts. Though the format of both tables 2 and 3 are the same that is IdNo (Autonumber) and someText (Text 50 characters).

I could not realy see if this would cause a problem since there is no king of index on this field in the main table.

I have changed this design and compacted and repaired the database. Just got to sit and wait again to see if it fails again.

Does anyone have any ideas about the nature of this databases ilness.

If you can please let me know.

Cheers CG084
 
I have recently encountered something similar:
I am currently maintaining a Frontend/Backend DB. Sometimes data could not be entered and I received a write conflict error. I could track it down to one user who was obviously not fully implemented yet.
Because: when this user logged in with a different LOGIN on the same machine, everything worked fine.

Since you have a multi-user environment too, this might be it.
See if you can track the problem down to a time, when one specific user is logged in. (you could simply take a look into the backend's ldb).

Hope this helps,
MakeItSo

Andreas Galambos
EDP / Technical Support Specialist
Bowne Global Solutions Wuppertal, Germany
(andreas.galambos@bowneglobal.de)
HP:
 
Are your data tables all in the same MDB file, or different ones?

Ed Metcalfe.

Please do not feed the trolls.....
 
Ed2000,

Just using the same mdb file for everything.


Take 2 databases in to the network. With New and improved wash and go i am just taking one database in to the mix.

Cheers cg084
 
I'd definitely split into a front end/back end setup for a start......

Ed Metcalfe.

Please do not feed the trolls.....
 
So far i have not split the database up. What i have done is to create a new database from scratch. Still this problem persists. I have other databases operating in both Access 97 and 2k versions on the same machines. Not a problem. Thhese other databases are a little more complex structure wise. But this database is very simple. 1 table for results with 2 tables being used as the source for 2 combo boxes on the main form. I do not really want to convert in to a front and a back end database since i believe the problem will still appear here as well.

What i propose to do is to create the database from new in Access 97.

This problem is still bugging me. I have been told by our field service department here that the problem lies in the huge number (No more than 7 people) who are using the database at the same time.

Does anyone have any more ideas.
The problem keeps persisting and is starting to annoy.

Cheers for any help.
CG084
 
Actually, up to 70 persons are working with my one of my DBs - no problems so far. However I have recently found out, that in Access 97 it might have to do with a database variable like
Dim db as (DAO.) Database
Set db = CurrentDb

But the db variable is not released correctly (in some module) then this might lock your database. have you checked your modules for such a thing?

MakeItSo

Andreas Galambos
EDP / Technical Support Specialist
Bowne Global Solutions Wuppertal, Germany
(andreas.galambos@bowneglobal.de)
HP:
 
In the Access 2k database the only VB present so far is whatever has been created by the switchboard wizard and coding to close the current form when a button is clicked.

After being told by some of the users it appears now as if a couple of users. The same ones each time may have a different set up on Access that may interfere with settings of other group members. I was told that as soon as person x and person y exit out of the database it appears to run ok.

Something to look at tomorrow. In the mean time i am just going to sit and wait. Since i have Created a new 2k db and now an access 97 db. If it goes wrong again it is not any database problem and more likely to be something else.

Cheers for any help.
CG084
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top