ODBC
Driver
The ODBC
driver is an ODBC
3
driver that works with the database engine
used in our software. All registered customers of CyberMatrix database
software are given access to this driver free of charge. The ODBC
driver works with newer non-enterprise versions of our
software
(Class Scheduler v3+, CyberMatrix Office, Employee
Project Clock v2.20+, Employee Scheduler, In Out Scheduler, Meeting
Manager v4+, Phone Lister, Point Of
Sale, Project Clock v5.10+, Pro Schedule v3+, Timesheets).
The ODBC
driver can be used
to successfully access CyberMatrix
application data from Microsoft
Data Access Components (MDAC)
2.7 or higher and the following applications:
• Crystal
Reports 8.5 and 9 (Version 9 requires a patch in order to
run correctly. Please see the
technical bulletin regarding this issue for more information:Problems
with ODBC Driver and Crystal Reports 9).
There are problems with Crystal Reports 10 in general due to the fact
that Crystal keeps breaking the ability of Crystal Reports to work with
ODBC drivers that use backslashes in catalog names like this ODBC
driver does.
• MS Query
(and subsequently mail-merge in Word and external data in Excel)
(Office 2000) [DBISAM ODBC driver only]
• Microsoft Office 2000
and later (Microsoft Access has problems with using an auto-increment
field as
part of the primary index since the Jet engine cannot "discover" the
keys properly when they are not populated explicitly by the client
application.)
• Microsoft Visio 2000 and later
• BDE
(Borland Database Engine) 5.01 and later (With the BDE there are
problems with using an auto-increment field as
part of the primary index since the BDE cannot "discover" the keys
properly when they are not populated explicitly by the client
application.)
• ODBCExpress
5.06 and 7
• ADOExpress
• Microsoft IIS
ASP (5
and later. It is recommended that you only use the ODBC functionality
in ASP and
not the ADO->OLEDB->ODBC bridge driver through the ADO
functionality. The bridge driver does not function correctly in most
cases.)
• Microsoft Visual Basic 6 and
later (It is recommended that you only use the ODBC functionality in VB
6 and
not the ADO->OLEDB->ODBC bridge driver through the ADO
functionality. The bridge driver does not function correctly in most
cases.)
• Microsoft Visual Studio
.NET 2002 and later (It is recommended that you only use
the ODBC.NET data provider and not
the ADO->OLEDB->ODBC bridge driver through ADO. The
bridge driver
does not function correctly in most cases.)
Missing Features
There
are still a few things missing from
the driver, but they should
not affect most environments. These missing items are:
• Support for bulk operations (specifically the
SQLBulkOperations call)
• Support for many ODBC extended scalar functions
More Information
The driver
can completely handle all
updating of data via SQL
statements and the SQLExecute or SQLExecDirect calls, including BLOB
data. Parameters are also completely supported, including BLOB
parameters.
The driver provides scrollable cursor support via SQLFetchScroll and
SQLExtendedFetch. The only two types of scrollable cursors supported
are Static and Dynamic. Keyset-Driven cursors are not supported.
The driver cannot performed positioned updates using the SQL syntax
WHERE CURRENT OF and using the SQLSetCursorName and SQLGetCursorName
calls. This functionality is not supported in the database
engine.
Even though the driver supports parameter arrays, you still cannot
request multiple result sets with the SQLMoreResults call. This is not
supported in the database engine. You will, however, be able
to execute
multiple INSERT, UPDATE, or DELETE statements.
1
Problems with ODBC Driver and
Crystal Reports 9
There is an issue with the
original Crystal Reports 9 when verifying the database in a report that
uses the ODBC driver. The following error message appears:
"The
database table <TableName> cannot be found. Proceed to
remove this table from the report?"
Crystal has
issued a hot fix to resolve this problem and you can download it from
this link:
ftp://ftp.crystaldecisions.com/outgoing/ehf/cr90dbexwin_en.zip
In
their ReadMe PDF file included with the hot fix they describe the
problem incorrectly, but the fix does resolve the problem. They
indicate that the fact that the ODBC Driver doesn't support
catalogs is the source of the problem, however this is not the case.
The ODBC Driver does indeed support catalogs, rather the
problem is that Crystal Reports 9 was parsing catalog names that are
also directory names, such as is the case with local catalog names, and
treating everything after the first backslash as a schema name even
though the ODBC Driver specifically reports that it does not
support schema names. Previously with Crystal Reports 8.5, these types
of catalog names were kept intact, as they should be because that is
what the ODBC Driver indicates is the catalog name.
