1) Install MyODBC on Windows machine.
2) Create "linked" tables using MyODBC to define MySQL tables to Access.
3a) First time through: Use MS Access to back up data to new tables defined on MySQL, to get the structures in place. Then, in MySQL, define appropriate indexes.
3b) Future times through: Use a MS Access macro to delete all rows from the MySQL tables and then insert from the Access tables into their equivalents using "insert into x select * from y" syntax.
Is this a good approach? Is there a better one?
Now, the long version, in case I'm asking the wrong questions...
The bigger problem is that I want to publish the contents of SmartListToGo (SLTG) tables on PalmOS on the web. My plan is to synchronize the tables to MS Access tables, which I can do using SLTG software, and then somehow make the data available to PHP running with Apache on my Linux box. Initially I had intended to use ODBC to allow the Linux machine access to the MS Access tables, using OpenLink Software's product line, which I believed from the PHP FAQ to have a free-for-personal-use version of software which would allow this. However, on OpenLink's web site, I saw no such thing (for free, that is).
So, I'm falling back to duplicating the Access data in MySQL, which is clearly not as attractive a solution -- it requires duplicating all data Yet Again, and manually refreshing the data whenever I synchronize my Visor. I suppose I could use ASCII files instead of MySQL tables, but I have MySQL running anyway, and although the tables are small (a few hundred rows in each of about 8 tables), there's a lot of joining going on.
Better ideas are welcome.
Thanks! Bruce Feist
--------------------------------------------------------------------- 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