Simon, Several issues come to mind.
First, as Tim suggested, make sure ODBC logging is turned off. It should be by default but if you turn it on, it will whip your HD like a bad puppy. Second, run MySQL on a different machine. More importantly, understand the difference between Access and MySQL (If you do already then skip this chapter) MySQL is a database server. Access is a desktop database. It takes more horses to run MySQL than Access because it does more. If all you need is a single user database running on your desktop (Keep your recipes, checkbook, etc.) Then Access is an adequate tool. (I prefer Visual FoxPro for these tasks, but that's just me) If however, you are developing any sort of multi-user application then you'd be a fool to use Access. Like FoxPro and dBase before it, it just was not designed to run like that. Yes, it has been patched and kludged to death to make it seem like this works but when you get right down to it, it just can't do the job. So you turn to a database server. In walks MySQL. MySQL will not allow you to pain forms and reports. It is first and foremost a database engine with EVERYTHING else left for a client to do. It will allow you to safely store and retrieve your data, assign rights to multiple users, and - if compiled correctly - give you a transaction safe environment for your work. So it may seem that on your machine, with both MySQL and Access loaded together Access runs ever so much faster. However, you are comparing single use Access to single use MySQL. (also, once mysql starts caching things, it gets faster. The more you use it, the faster it runs!) Also, once you get MySQL into it's native environment (server class machine or at least one where nothing else is going on) it will run like a screaming banshee. At the risk of pissing off all your windows users out there (Check my headers, created with Outlook, I use it too) Run MySQL on a *nix box of some kind. Without the overhead of the graphical interface, which just gets in the way on a server, you have more horses/RAM to run the important stuff. In short: MySQL != "Drop in replacement for desktop database" =C= * * Cal Evans * Journeyman Programmer * Techno-Mage * http://www.calevans.com * -----Original Message----- From: Simon Ashby [mailto:[EMAIL PROTECTED]] Sent: Monday, July 01, 2002 4:58 AM To: MYSQL Subject: Speed issue Hi I am trying to move an Access 2000 database into MYSQL 3.27.47nt running on a Win2K machine. MYODBC with the 3.51 drivers is also installed. MYSQL is running and readily responds to SQL queries using the DOS window at the mysql> prompt. However, when linking the MYSQL database with ADO and VB6 the response is slow and there is a lot of disk activity before an answer is returned. It is a lot slower than the original Access2000/VB6 setup. A DSN-less code is being used to link VB6/ADO to MYSQL. The connection string is listed below: con.ConnectionString = "DRIVER={MySQL ODBC 3.51 Driver};" _ & "SERVER=localhost;" _ & " DATABASE=GIS;" _ & "UID=Admin;PWD=africa; OPTION=16386" If of any relevance, within the WinMySQLAdmin on the Environment Tab, MYODBC is stated as not found eventhough it has been loaded. Any pointers on how to get rid of the disk churning and get a normal response in this set up would be much appreciated. Thanks Simon --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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
