[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 619
  • Last Modified:

Write conflict

I have been running a medical application successfully in one hospital for ~4 years.  It consists of an MS Access GUI with SQL server backend.  I have recently created a second instance on a virtual server in another institution, using same GUI, same SQL database.  However, I am now getting write conflict messages from the Access GUI.  This occurs even when a single record is being accessed by a single user, although multiple users may be accessing the same table concurrently.  MS Access is set to 'No lock'.

This does not occur in the first institution, and I suspect there may be something causing this in the 2nd environment, but cannot figure it out.  Any help or suggestions would be gratefully received.
0
pjstow
Asked:
pjstow
  • 2
  • 2
1 Solution
 
TommyTupaCommented:
I had a similar problem resolved by adding a default value to my bit fields and a timestamp column to sql server.  The timestamp column isn't actually a timestamp but a GUID that gets updated every time a row is updated.  Here are two links which discuss the problem.

1) http://support.microsoft.com/kb/280730
2) http://groups.google.com/group/comp.databases.ms-access/browse_thread/thread/7a5d86137f410687/d9c1bf173b19f687?hl=en&q=avoid+write+conflicts+sql+group:*access*#d9c1bf173b19f687
0
 
Jeffrey CoachmanCommented:
1. <I have recently created a second instance on a virtual server in another institution>
Access is not meant to be run in this way.
Why not just install the application for this other institution?

2. Is the database "Split"

0
 
pjstowAuthor Commented:
TommyT:  Thanks for the useful references.  A timestamp has fixed the problem.  If only the rest of life were so simple.  Thankyou +++

boaq2000:  Sorry, but I cannot have explained the problem adequately.  The institutions are entirely separate with separate SQL database and Access GUI at each site.  It's merely that the problem arose at one site, and not the other.  May be related to volume of use, or just work practices.  See above.  I'm happy.
0
 
Jeffrey CoachmanCommented:
OK,

Sorry if I misunderstood you.

Jeff
0
 
pjstowAuthor Commented:
Thanks for your advice.  My problem has been solved.  I have also made subtle changes to the GUI to smooth the process.
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now