Write Conflict Error

[kitty77]

So, yesterday I was having an issue with QuickBooks and multi-user function. A tech from QuickBooks remoted in and changed some things on my computer that has the QuickBooks file. That same computer also holds my Access Database. I did not actually witness what might have been changed.

So, all of a sudden, I'm getting a "Write Conflict" error. Does anyone know what might I look for that could affect this? Maybe they changed a service or something.
If I open my database with only one user in it at a time, it works just fine.

Thanks...

 

[bob fitz]

Is your db split, with each user having their own front-end and each front-end linked to tables in a single back-end file?

 

[kitty77]

Yes

 

[kitty77]

Does anyone have any ideas on this?

 

[jdraw]

Good starting point may be to talk with the QB tech and ask/document exactly what was done. I'm surprised that wasn't recorded. Also,no mention of a backup before tech intervention.

Do you have details on the "Write Conflict" error?
Did you record details of the issue for which you decided to call the QB tech?

May be just me, but there is a paucity of detail in your thread.

 

[ebs17]

Does anyone know what might I look for that could affect this

Errors usually don't just appear out of nowhere, but rather follow certain situations that need to be described. If you know what you are doing, you can analyze this situation => write environment in this code and instructions.
As a affected being, you complained and cried. Now act like a technician.

 

[The_Doc_Man]

Does the Access database touch the Quickbooks file in any way?

A spontaneous "write conflict" that didn't occur before that intrusion and now crops up means that one of two things might have happened.

First, the tech might have played with folder permissions at a root or first-level directory AND allowed the permissions to propagate. So this might be a permissions problem. Verify that you still have MODIFY permission on the folder holding the DB files as well as the DB files themselves. The write conflict might be because of a problem with the .LDB or .LACCDB file suddenly being exclusive.

Second, the tech might have dinked around with something in the registry. (IF he did so without first telling you, complain to his supervisor!!!!) In that case, I'm not up on ALL of the possible registry settings. They have... shall we say... proliferated since the days of Win 3.2 and DOS shells.

I cannot recall offhand of a general Windows security setting (i.e. Start >> Settings >> Security) that would lead to write conflicts. Normally, Microsoft doesn't want to give its users that much power over what is truly a can of worms at the internal controls level. Which is why I questioned a possible registry hack.

 

[The_Doc_Man]

Errors usually don't just appear out of nowhere, but rather follow certain situations that need to be described. If you know what you are doing, you can analyze this situation => write environment in this code and instructions.
As a affected being, you complained and cried. Now act like a technician.

Show a little compassion there. We have folks of all levels of experience and SOME of them might not be as well versed as you are in trying to fix problems. Hell, I even have to ask for a hint now and then, and I was working in the computer industry as early as 1975, before PCs became widely used. And I had been involved with computers during my college days starting as early as 1967 when all the computers were still 2nd generation machines - boards full of discrete transistors, still waiting for the invention of the microchip.

Kitty77 was looking for advice, not a shoulder to cry on.

 

[gemma-the-husky]

Is the QuickBooks issue actually anything to do with the access database?

Is it access or QB giving you the error?

 

[isladogs]

Does anyone have any ideas on this?

I don't use Quickbooks so can't offer specific guidance. However you might find something useful in my article on this error

Write Conflict Errors

This article explores some of the causes of the 'dreaded' write conflict error and how to deal with those issues.

www.isladogs.co.uk

 

[kitty77]

Errors usually don't just appear out of nowhere, but rather follow certain situations that need to be described. If you know what you are doing, you can analyze this situation => write environment in this code and instructions.
As a affected being, you complained and cried. Now act like a technician.

Don't bother!!

 

[kitty77]

Does the Access database touch the Quickbooks file in any way?

A spontaneous "write conflict" that didn't occur before that intrusion and now crops up means that one of two things might have happened.

First, the tech might have played with folder permissions at a root or first-level directory AND allowed the permissions to propagate. So this might be a permissions problem. Verify that you still have MODIFY permission on the folder holding the DB files as well as the DB files themselves. The write conflict might be because of a problem with the .LDB or .LACCDB file suddenly being exclusive.

Second, the tech might have dinked around with something in the registry. (IF he did so without first telling you, complain to his supervisor!!!!) In that case, I'm not up on ALL of the possible registry settings. They have... shall we say... proliferated since the days of Win 3.2 and DOS shells.

I cannot recall offhand of a general Windows security setting (i.e. Start >> Settings >> Security) that would lead to write conflicts. Normally, Microsoft doesn't want to give its users that much power over what is truly a can of worms at the internal controls level. Which is why I questioned a possible registry hack.

Thanks Doc. I've looked at all the permissions, folder, etc.. all look correct with the "modify" permission applied.