:: DEVELOPER ZONE
MySQL Reference Manual :: 25.1.11.11 I Have Very Long Tables. What is the Best Configuration for MyODBC to Access These Tables?
Search the MySQL manual:
- 25.1.11 MyODBC and Microsoft Access
- 25.1.11.1 How to Set Up Microsoft Access to Work with MySQL using MyODBC?
- 25.1.11.2 How to Export a Table or Query from Access to MySQL?
- 25.1.11.3 How to Import or Link MySQL Database Tables to Access?
- 25.1.11.4 The Structure or Location of a Linked Table has been Changed. Can I See Those Changes Locally in Linked Tables?
- 25.1.11.5 When I Insert or Update a Record in Linked Tables, I Get #DELETED#
- 25.1.11.6 How Do I Handle Write Conflicts or Row Location Errors?
- 25.1.11.7 Whenever I Export a Table from Access 97, a Strange Syntax Error Occurs
- 25.1.11.8 Access Returns Another user has modified the record that you have modified While Editing Records
- 25.1.11.9 How to Trap ODBC Login Error Messages in Access?
- 25.1.11.10 How Do I Optimize Access for Performance with MyODBC?
- 25.1.11.11 I Have Very Long Tables. What is the Best Configuration for MyODBC to Access These Tables?
- 25.1.11.12 How to Set the QueryTimeout Value for ODBC Connections?
- 25.1.11.13 INFO: Tools to Export/Import from/to Access to/from MySQL
Additional languages
Additional formats
If you have very large (long) tables in Access, it might take a
very long time to open them. Or you might run low on virtual memory
and eventually get an ODBC Query Failed error
and the table cannot open. To deal with this, select the following
options:
Return Matching Rows (2)
Allow BIG Results (8).
These add up to a value of 10 (OPTION=10).
© 1995-2005 MySQL AB. All rights reserved.
User Comments
Warning: query failed: Unknown column 'user.firstname' in 'field list' in /data0/sites/live/web-main/lib/mysql-cxn.php on line 69
Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /data0/sites/live/web-main/lib/docbook.php on line 245
Add your own comment.