Record Locking Help PLease

[James Dudden]

Hi,

I have a multi user Access97 database with a single back end and single front end. Multiple users have the database open at any one time.

The problem is when they are editing the same record - one of the persons edits gets lost.

What i need to do is stop this from happening. I know this can be done with record locking but the user doesn't find out until they try to save and end up wasting loads of time and effort.

Can something be implemented to warn the user as soon as they start editing a record that is already being edited?

Many thanks for any help on this

Regards

James

 

[Rabbie]

Any multi-user database should be split otherwise you WILL get data corruption. Each user should have their own copy of the FE.

 

[James Dudden]

We run the database with only one front end as it is being constantly updated - it would be a huge job to alter many differnet copies with many potential problems.

 

[Rabbie]

We run the database with only one front end as it is being constantly updated - it would be a huge job to alter many differnet copies with many potential problems.

That's your choice. You will get data corruption but if you can live with that. Have you seen Bob Larson's tool for keeping FEs in step. You might find it useful.

 

[tokoloshi]

Record locking issues

Can I add to that question please?

I would like to implement some of the advanced record locking capabilities available in SQL Server 2005 as the BE environment within my apps.

The isolation levels provided natively by Access level much to be desired.

Anybody had any joy in this space?

I am particularly thinking of the snapshop record locking functionality of SQL Server.

NOTE: For those of you who do not dabble in SQL Server - it really is no big mystery, neither is it expensive. SQL Server Express is for free and is an excellent environment to develop in.