> From: MB Software Solutions <[EMAIL PROTECTED]> > I'm putting new functionality into some software that started using VFP > (and still does primarily) as the backend, but for these new things I'm > creating the tables in a MySQL database. I'm aware of some caveats of > doing this (like synchronization, and as such, I'm avoiding it where > this would be the case but instead really just using it for lookup > tables and user administration/rights), but wondered what other caveats > folks might think of for this?
Caveats? 1) How was your key generated in VFP data? 2) How did you verify the key for secondary immediate use? 3) Why would you do a mix and not convert to all MySQL? 4) That reindex code is not longer going to be used. 5) Exclusive use, what for? 6) Pack This! 7) All your code that referenced and ! deleted() will need to be changed. 8) Do you know how to make MySQL backups and restore from them? 9) Do you ever truncate the ib_logfile? _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
