Hi I have developed several apps using Access/ADO front end via MyODBC with MySQL back end over the last couple of years. There are 2 problems that I come across time and time again, and I wondered if anyone could throw any light on these. To recreate these I made a table on my MySQL server called 'test' with the following definition: TestID | int(8) | | PRI | 0 | auto_increment | timastamp | timestamp(14) | YES | | NULL | | blah | varchar(10) | YES | | NULL | Then I linked to it through MyODBC 2.50.32 with options 'Don't optimise column width' and 'Return matching rows' selected. Then I linked it to Access 97. Open the table and enter some records. You will see that after a few records have been added all the records become the same as the one you just entered. Now keep entering records until Access is forced to create a scroll bar and scroll down. Now you *may* see the #record is deleted# error (all records from now in will come up with #record is deleted# in all columns) - sometimes it happens, sometimes it doesn't - I have no idea why. If you don't see *either* of these problems, please could you reply with the version of MySQL and MyODBC that you have, as I would dearly like to eliminate these problems. Otherwise if you have any ideas I would be very grateful for help - these issues are forcing us to look away from MySQL in the future at databases which work successfuly through ODBC. Thanks for your time :) Jason Handscombe Systems Manager Infratest Burke UK --------------------------------------------------------------------- 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
