List:MySQL ODBC« Previous MessageNext Message »
From:Ed Carp Date:March 23 1999 1:22pm
Subject:Re: Write Conflict in Access97, ODBC 2.50.22
View as plain text  
I guess you just subscribed.  Christian Mack answered this question almost
exactly 24 hours ago:

"Peter F. Brown" wrote:
>
> Dear Folks,
>
>    I'm trying to update records from Win95 to local tables on my
> Win95 machine and also remote records running under Linux.
>
>    I've used a number of different Win95 clients, such as Visual dBASE,
> and some others, and I keep getting the intermittent error message:
> "couldn't perform the edit because another user changed the record"
> (or something to that effect.)
>
>    Has someone run across this? I know that no one else is using the
> tables. Is it an ODBC problem, or something else?
>
>    Thanks!
>
> Peter F. Brown

Hi Peter

You must have one TIMESTAMP and a PRIMARY KEY in each table you use with
MS-programs via ODBC.
Without them you get the above error message.

Tschau
Christian


---------------------------------------------------------------------
To request this thread, e-mail myodbc-thread79@stripped
To unsubscribe, e-mail the address shown in the
List-Unsubscribe header of this message.
For additional commands, e-mail: myodbc-help@stripped


--
Ed Carp, N7EKG - erc@stripped - 9403672744@stripped for URGENT
messages only!
Web: http://www.pobox.com/~erc

"There are three kinds of lies: lies, damn lies .. and then there's Bill
Clinton"
-----Original Message-----
From: Foley, John <John.Foley@stripped>
To: myodbc@stripped <myodbc@stripped>
Date: Tuesday, March 23, 1999 7:02 AM
Subject: Write Conflict in Access97, ODBC 2.50.22


>
> Hi all, I was wondering if anybody had come across this one yet . .
>.
>
> I am using Access97 with ODBC 2.50.22 and MySQL 3.22.16a-gamma for
>pc-solaris2.7 on i386
> (recently upgraded from 2.50.18 and 3.21.xx in an attempt to overcome the
>same problem) and am unable
>to edit a row in a table (a mysqldump of which lies below). I can add
>records, just not edit them.
> Access gives the error message:
> "Write Conflict"
> "This record has been changed by another user since you
>started editing it. If you
> save the record, you will overwrite the changes the other
>user made."
> "Copying the changes to the clipboard will let you look at
>the values the other user . . ." yada yada.
>
> This table should not be in use by anybody else, as the database is
>in early development,
>and I'm the only developer.
>
>
>
> For reference sake, the database has a number of tables, all of
>which have "NPB int(10)" as the primary key.
>Could this be caused by a lock on another table, given the identical key
>names?
>
>
>
>
>
>
># MySQL dump 5.12
>#
># Host: localhost    Database: PDP_Pub
>#--------------------------------------------------------
># Server version 3.22.16a-gamma-log
>
>#
># Table structure for table 'PPEActivity'
>#
>CREATE TABLE PPEActivity (
>  NPB int(10) DEFAULT '0' NOT NULL,
>  TeamLeadEngg smallint(5) DEFAULT '0',
>  PPEStatus tinyint(3) DEFAULT '0',
>  PhaseChg0_1 datetime DEFAULT '0000-00-00 00:00:00',
>  PhaseChg1_2 datetime DEFAULT '0000-00-00 00:00:00',
>  PhaseChg2_3 datetime DEFAULT '0000-00-00 00:00:00',
>  PhaseChg3_4 datetime DEFAULT '0000-00-00 00:00:00',
>  PhaseChg4_5 datetime DEFAULT '0000-00-00 00:00:00',
>  POType tinyint(4) DEFAULT '0',
>  PPEAction text,
>  PPEActionDate datetime DEFAULT '0000-00-00 00:00:00',
>  PRIMARY KEY (NPB)
>);
>
>#
># Dumping data for table 'PPEActivity'
>#
>
>INSERT INTO PPEActivity VALUES (5597,1,2,'0000-00-00 00:00:00','1999-01-01
>00:00:00','0000-00-00 00:00:00','0000-00-00 00:00:00','0000-00-00
>00:00:00',2,'complete doublelock','1999-03-15 00:00:00');
>
>
>
>
>
> John
>
>---------------------------------------------------------------------------
-
>----------------------------------
> John T. Foley, CAD Systems Administrator
> Pollak Actuator Products Division, A STONERIDGE Company
> ph: 617-282-9550 x266 fax: 617-282-9058
>---------------------------------------------------------------------------
-
>----------------------------------
>
>
>---------------------------------------------------------------------
>To request this thread, e-mail myodbc-thread84@stripped
>To unsubscribe, e-mail the address shown in the
>List-Unsubscribe header of this message.
>For additional commands, e-mail: myodbc-help@stripped
>
>

Thread
Write Conflict in Access97, ODBC 2.50.22John Foley23 Mar
  • Re: Write Conflict in Access97, ODBC 2.50.22Peter Carter24 Mar
Re: Write Conflict in Access97, ODBC 2.50.22Ed Carp23 Mar