Re: Solution What's Up with this #Deleted Thing
I create the [TimeStamp] field in Access and set the value initially to #01-01-2000#, and then again to [TimeStamp] + [RecordID]/86400, making it unique to the second. [RecordID] is an auto-number field. By dividing by 86400, the number of seconds in a day, each record has a unique TimeStamp value.
After exporting, I run a pass-through query to change the schema:
ALTER TABLE `mydatabase`.`mytable`
MODIFY COLUMN `RecordId` INTEGER NOT NULL AUTO_INCREMENT,
MODIFY COLUMN `TimeStamp` TIMESTAMP,
ADD PRIMARY KEY(`RecordId`),
ENGINE = MYISAM;
I think that I've avoided the #Deleted error because I export this way; and exporting is flawless. Even on tens of thousands of records in dozens of tables, performed over and over again.
However, I created another problem. If I have one or more of my Access/MySql applications open when I export and modify a "large" amount of data, the Access application may suffer from Run-time error '2486`. Not everytime, and not on all computers. I thought I had this problem solved, but it pops up during this high-activity session.