<< previous page   --   table of contents   --   next page >>
| | | | | | | |
  • Return to Table of Contents
    • Table of Contents
    1. General Information
    2. MySQL Installation
    3. Tutorial Introduction
    4. Database Administration
    5. MySQL Optimisation
    6. MySQL Language Reference
    7. MySQL Table Types
    8. MySQL APIs
    9. Extending MySQL
    Chapter 8:  MySQL APIs 549 8.3.4  How to Report Problems with MyODBC MyODBC has been tested with Access, Admndemo.exe, C++-Builder, Borland Builder 4, Cen- tura Team Developer (formerly Gupta SQL/Windows), ColdFusion (on Solaris and NT with svc pack 5), Crystal Reports, DataJunction, Delphi, ERwin, Excel, iHTML, FileMaker Pro, FoxPro, Notes 4.5/4.6, SBSS, Perl DBD-ODBC, Paradox, Powerbuilder, Powerdesigner 32 bit, VC++, and Visual Basic. If  you  know  of  any  other  applications  that  work  with  MyODBC,  please  send  mail  to myodbc@lists.mysql.com about this! With some programs you may get an error like:  Another user has modifies the record that you have modified.  In most cases this can be solved by doing one of the following things:    Add a primary key for the table if there isn't one already.    Add a timestamp column if there isn't one already.    Only use double oat elds.  Some programs may fail when they compare single oats. If the above doesn't help, you should do a MyODBC trace le and try to gure out why things go wrong. 8.3.5  Programs Known to Work with MyODBC Most programs should work with MyODBC, but for each of those listed here, we have tested it ourselves or received con rmation from some user that it works: Program Comment Access To make Access work:    If you are using Access 2000, you should get and install the newest (ver- sion 2.6 or above) Microsoft MDAC (Microsoft Data Access Components) from http://www.microsoft.com/data/.  This will x the following bug in Access:  when you export data to MySQL, the table and column names aren't speci ed.  Another way to around this bug is to upgrade to MyO- DBC Version 2.50.33 and MySQL Version 3.23.x, which together provide a workaround for this bug! You should also get and apply the Microsoft Jet 4.0 Service Pack 5 (SP5) which can be found here http://support.microsoft.com/support/kb/articles/Q 239/1/14.ASP.   This  will   x  some  cases  where  columns  are  marked  as #deleted# in Access. Note  that  if  you  are  using  MySQL  Version  3.22,  you  must  to  apply  the MDAC patch and use MyODBC 2.50.32 or 2.50.34 and above to go around this problem.    For all Access versions, you should enable the MyODBC option ag Return matching rows.  For Access 2.0, you should additionally enable Simulate ODBC 1.0.
     

    Customer Support CentreMySQL Reference Manual

    Web Hosting Services
    UNIX WEB HOSTING
    MERCHANT ACCOUNTS
    DEDICATED SERVERS
    E-COMMERCE HOSTING
    SUPPORT & FAQ's
    TERMS OF USE
    Domain Services
    DOMAIN
    REGISTRATION
    MANAGE
    YOUR ACCOUNT
    SUPPORT & FAQ's
    TERMS OF USE
    Corporate Info
    ABOUT US
    OUR NETWORK
    CONTACT US
    SITE MAP
    UNIX Web Hosting | Merchant Accounts | Dedicated Hosting | E-Commerce Hosting
    Domain Registration | About Us | Our Network | Contact Us | Site Map
    Our Partners
    Copyright © 2002 Dyntex Group, Inc. All Rights Reserved
  • Return to Table of Contents
    		•
  • Back to top
    • Web Hosting: Manuals & FAQ's
    1. Unix-Based Web Hosting
    2. Unix Dedicated Servers
    3. Windows Dedicated Servers
    4. CuteFTP User’s Guide
    5. CuteHTML User’s Guide
    6. WS_FTP Pro User's Guide
    7. Miva Order User's Guide
    8. Miva Merchant User's Guide