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 Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Opinion Please

Status
Not open for further replies.

pleg12345

IS-IT--Management
Dec 21, 2003
48
EU
Hi im building a query logging database, which will be used by several people on a server. I have implemented the data capture form, and was wondering what would be the best way to search for previous records and make amendments.

Due to concurrency issues i thought MS Access might have a few problems with more than one person accessing the same record and amending them at the same time?

Please can somebody explain what would be best in this situation, i.e making a search form using a filter?
 
Access will certainly have a problem with that but then, so will any DBMS. The difficulty is obviously that it is unclear what should happen when

[li]User A starts to edit a record.[/li]
[li]User B starts to edit the same record[/li]
 
Sorry ... sent too soon.

Access will certainly have a problem with that but then, so will any DBMS. The difficulty is obviously that it is unclear what should happen when


[li]User A starts to edit a record.[/li]
[li]User B starts to edit the same record.[/li]
[li]User B finishes and saves.[/li]
[li]User A finishes and saves.[/li]

Now ...

Should User B be allowed to start editing in step 2?
Should he be allowed to save in step 3?
Should A be allowed to save in step 4?
What should the content of the record be after step 3? After step 4?

Until you resolve those issues for your specific situation there is really no way that the database can "handle" it for you ... regardless of which DBMS it is.
 
You should try to design your system so this is unlikely to happen. For example have different users responsible for different sets of records. Why would more than one person need to update the same record at the same time? Sounds like job duplication? Maybe you can have each user have their own sets of queries and they can update only their own? And why would you need to update a log, I would have thought this should be specifically prohibited.
 
Can't you have the records locked up depending who access the record first? If you have the record locked then no one else except the first user who opens it up.

-Laughter works miracles.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top