Oracle 5.0 Reference Manual page 1832

Error with SELECT COUNT(*)
Using
SELECT COUNT(*) FROM tbl_name
This error occurs because the
make sense of a number this big. Select the
16384).
Multiple-Step Operation Error
Using the
AppendChunk()
generated errors. Check each status value
The
GetChunk()
location is specified as adUseServer. On the other hand, you can overcome this error by using
adUseClient.
A simple example can be found from
Modified Record Error
Access returns
editing records on a Linked Table.
In most cases, this can be solved by doing one of the following things:
• Add a primary key
• Add a timestamp column if one doesn't exist.
• Only use double-precision float fields. Some programs may fail when they compare single-precision
floats.
If these strategies do not help, start by making a log file from the ODBC manager (the log you get when
requesting logs from ODBCADMIN) and a Connector/ODBC log to help you figure out why things go
wrong. For instructions, see
Direct Application Linking Under Unix or Linux
When linking an application directly to the Connector/ODBC library under Unix or Linux, the application
crashes.
Connector/ODBC under Unix or Linux is not compatible with direct application linking. To connect to an
ODBC source, use a driver manager, such as
Microsoft Office and DATE or TIMESTAMP Columns
Applications in the Microsoft Office suite cannot update tables that have
This is a known issue with Connector/ODBC. Ensure that the field has a default value (rather than
NULL) and that the default value is nonzero (that is, something other than
INFORMATION_SCHEMA Database
When connecting Connector/ODBC 5.x to a MySQL 4.x server, the error
user 'xxx'@'%' to database 'information_schema'
Connector/ODBC 5.x is designed to work with MySQL 5.0 or later, taking advantage of the
INFORMATION_SCHEMA
planned for the final release.
S1T00 Error
When calling SQLTables, the error
for Connector/ODBC.
Connector/ODBC Notes and Tips
COUNT(*)
or
GetChunk()
and
AppendChunk()
http://www.dwam.net/iishelp/ado/docs/adomth02_4.htm
Another user had modified the record that you have modified
for the table if one doesn't exist.
Section 20.1.4.8, "Getting an ODBC Trace
database to determine data definition information. Support for MySQL 4.1 is
S1T00
within Visual Basic and ASP returns an error.
[970] expression is returning a BIGINT, and ADO cannot
Change BIGINT columns to INT
ADO methods, the
error is returned.
methods from ADO do not work as expected when the cursor
or unixODBC.
iODBC
is returned, but I cannot find this in the list of error numbers
1812
option (option value
Multiple-step operation
File".
or
DATE TIMESTAMP
0000-00-00
1044 Access denied for
is returned.
while
columns.
00:00:00).