>>>>> "Juergen" == Juergen Hoffmann <jh@stripped> writes:
Juergen> On Mon, Jul 26, 1999 at 08:09:07AM -0400, Pat Sherrill wrote:
>> ----- Original Message -----
>> From: Juergen Hoffmann <jh@stripped>
>> To: <myodbc@stripped>
>> Sent: Monday, July 26, 1999 2:49 AM
>> Subject: MyODBC and Access 97
>> > Hello everyone,
>> > just like you suggested I added a timestamp(14) field to the Table also I
>> > have an ID Field which is auto increment and the primary key. I still get
>> > the same error message from Access 97: Somebody else is trying to write to
>> > the record at the time you tried to... Although I am the only guy
>> You may have an existing empty column from prior manipulation (i.e. prior to
>> adding the timestamp and primary key) of the tables. Check your data,
>> sometimes Access will create an empty row, I have seen this throw the error
>> you describe as well.
>> If this doesn't help, I'd be happy to look at your database, assuming it is
>> not huge.
Juergen> Hello everyone,
Juergen> could it be that there is a compatibility Problem between older MyQDBC
Juergen> Drivers and newer versions? Because using the old Driver 2.50.17 solved the
Juergen> Problem. Does anyone know, what the old option 2 converts to in the newer
Juergen> This seems to be really strange so I am posting the setup:
Juergen> MySQL Server 3.21.30
Juergen> MyODBC 2.50.22 then MyQDBC.dll from 2.50.17
Juergen> Office 97
Juergen> the new mdac_typg.exe installed on the client.
Juergen> Is this possibly a compatibility bug?
Juergen> Can anyone reproduce the error?
Juergen> kind regards
Juergen> Juergen Hoffmann
Could you do a myodbc trace in both versions and mail them to me so
that I can check what is different?
Option 2 = 'The second checkbox' = Return matching rows