I have followed two very simple rules and it has always fixed this 
problem for me.  First, every table must have an auto_increment field 
as the primary key.  I always name use the first field and I name it 
Serial.  Second, every table must have a timestamp field.  I use the 
second field and I name it DateChanged.  My current project consist of 
over 200 tables, 400 forms, and I don't know how many queries (They are 
hard coded into the forms.  I can explain why its done like that if you 
would like.)  In that project, and many others, I have followed those 
rules and it works flawlessly.  

Hope that helps,

[EMAIL PROTECTED]

-----Original Message-----
From: mysql-digest-help [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 13, 2001 5:24 AM
To: mysql
Cc: kevin
Subject: MyODBC 2.50.37 and Access 2000


Hi All,

I've installed MySQL 3.23.39 on my Windows 2000 Pro Server and I am
currently developing a database using Access 2000 as a front-end to 
MySQL
using MyODBC 2.50.37.

I have all my MySQL tables linked as ODBC tables in Access.

When I am inputting data into an Access Form and then save the record, 
all
the fields are changed to #DELETED.  The record data is saved I know, 
but
why do the fields all change to #DELETED when the record is inserted 
into
the MySQL table?  Is there a fix for this, or, it is just the case of 
using
ADO to do the insert and just refresh the Access Form to then move to 
the
record itself... a bit of a pain though...

Any ideas?

Many thanks,

Kevin Smith



---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to