Hi, I've been migrating an MS Access database from Access to use a MySQL linked-table backend. Most problems have been fixed by the advice on the MyODBC FAQ and other resources but I am having trouble with a sub form to which I cannot find an answer...
The database is a customers/stock/orders database. To place an order you select an option on the customer form which opens a new order record linked to the customer. Order-details are entered (such as payment) then a subform is used to enter items onto the order. But when you move onto the next item, any previous items show up as the item just entered, eg (imagine these >s are record selectors and _ is the cursor): Enter an item > 1_ And another > 1 > 2_ Try and enter a third and > 2 > 2 > _ Enter another, move and... > 3 > 3 > 3 > _ and so on. The data is fine if you requery the subform, and seems fine if you go back into the order and start entering data. The same happens if I create a new order record in ADO and open it up to start entering data. Access seems to be forgetting that it has added new items, because it keeps requerying the table for the subform with primarykey=null, if this helps explain what is happening. I have installed the latest Jet 4 SP5, MDAC 2.7, MyODBC 2.50.39, MySQL 3.22.32 (-6 Debian). It happens in Access 2000 and Access XP, with latest service packs. All the tables have a sensible timestamp and a primary key. Any ideas? --------------------------------------------------------------------- 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
