Board index MS SQL Server

Write Conflict with Access 2000 + SQL 7.0

Write Conflict with Access 2000 + SQL 7.0

Post by Ben Humphrey » Thu, 28 Oct 1999 04:00:00



Hi,

We have been running Access 97 backended with SQL 7.0 for about 6 months
with no real problems. I have just tried upgrading to Access 2000 and have
hit a problem. Even at table level, when editing existing records I get a
Write Conflict "This record has been changed by another user since you
started editing it...bla..bla...bla".

Any ideas? Am I using the right ODBC drivers. I loaded MDAC2.1 SP1 and was
using it with Access 97 ok!

--
Regards,

WEBSTER COMPUTER SYSTEMS - NSW
WWW: http://www.webster.com.au
Ph:  +61 2 9484 9944
Fax: +61 2 9484 9914

 
 
 
Top

Write Conflict with Access 2000 + SQL 7.0

Post by Paul Holme » Thu, 28 Oct 1999 04:00:00


Ben,

I can't help with this problem (although I think other people have solved
this by having adding a  timestamp column), but would be *very* interested
to hear if you've got long char columns working, i.e. varchar or nvarchar
where the length is greater than 255. I can't find anyone who's got this
working in A2K / SQL Server 7

Cheers - Paul

 
 
 
Top

Write Conflict with Access 2000 + SQL 7.0

Post by Ben Humphrey » Fri, 29 Oct 1999 04:00:00


Ok update time! I have some more information. If I load Access 2000 on the
server (NT 4.0) and run the frontend from there all is fine. But load up on
a Windows 98 machine and I get these write conflicts.
I'm going to try and access the database over the network from another NT
Server next.

--
Regards,


> Hi,

> We have been running Access 97 backended with SQL 7.0 for about 6 months
> with no real problems. I have just tried upgrading to Access 2000 and have
> hit a problem. Even at table level, when editing existing records I get a
> Write Conflict "This record has been changed by another user since you
> started editing it...bla..bla...bla".

> Any ideas? Am I using the right ODBC drivers. I loaded MDAC2.1 SP1 and was
> using it with Access 97 ok!

> --
> Regards,

> WEBSTER COMPUTER SYSTEMS - NSW
> WWW: http://www.webster.com.au
> Ph:  +61 2 9484 9944
> Fax: +61 2 9484 9914

 
 
 
Top

1. Write conflict - Access 2000 Mainform/Subform - SQL 7.0

I have problem and was hoping the someone could help me with it - I have a
main form with a number subforms most of these are views of the same table.
When I insert a new record into the table and the focus move from the main
form to the one of the subforms I get a "write conflict" error ( I'm the
only one using the database).

To fix the problem I created a procedure to trap the error using the main
forms "On Error" event property. The procedure looks as follows:

Private Sub Form_Error(DataErr As Integer, Response As Integer)

If DataErr = 7787 Then

Response = acDataErrAdded

End If

End Sub

Which stops the "write conflict" pop-up from appearing but does not save the
information and allow me to carry on, i.e. all the fields I just edited on
main form are reset - I was led to believe that setting the Response to
acDataErrAdded would fix this problem but for some reason it does not seem
to work. If anyone has any ideas why this or how to fix this sort of problem
please let me know.

BTW: My table is linked to a number of other tables, I have recreated all of
the links and checked that they are ok, I have also made sure that all
fields that are defined "bit" have default values ("0"). The database was
upsized from Access 2000 to SLQ 7.0 using the upsizing wizard.

2. Data-aware combo control

3. Write Conflict Error-Access 2000 SR-1 Link Tables to SQL Server 2000

4. Search for INFORMATIONS in FREE databases on the internet! - announce.htm (0/1)

5. Newbie, Stuck, Needs YOUR help!

6. SQL Server 2000 And Access 97 - Write Conflict

7. Concurrency problems

8. Access Data Project SQL Server 2000 write conflict

9. Write Conflict Errors with Access 2000 and SQL Server 7

10. Write Conflict Access 2000 with SQL 7

11. Write conflict error when updating data from SQL Server 7.0 in Access 97

12. Access 97 & SQL 7.0 - Write Conflicts


All times are UTC
Board index