Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

228 Chapter 10
Technical Articles
Introducing ODBCLink/SE
Client requirements:
486 processor at a minimum, preferably a Pentium
8 MB memory at a minimum, preferably 16 MB
5 MB of free disk space
Windows 3.1 or 3.11, Windows95, or WindowsNT V3.51 or 4.0
Microsoft or WRQ TCP/IP software
Software provided:
Server program for the HP 3000 or HP 9000 as appropriate
Client programs for both 16- and 32-bit platforms.
When using a 32-bit operating system, you should use the 32-bit
driver if possible. However, if you have a 16-bit application running
under Win95 or WinNT, you must install the 16-bit version of the
driver. On Windows95 or WindowsNT, you can run both the 16- and
32-bit versions of ODBCLink/SE. 16- and 32-bit data-sources are
maintained separately and coexist.
Dr. DeeBeeSpy from Syware Inc. for tracing calls to the ODBC driver
Migration from HP PC API
A data migration tool is provided to migrate data sources created for
HP PC API to ODBCLink/SE. Once the data sources are identified, the
translation is performed automatically.
Performance Considerations
ODBC access to the server is very fast. You should note the following
performance exceptions:
Reading and sorting a large table may prevent the server from
returning control to the client until the entire database has been
read and sorted.
Opening a large table in MS-Access will cause a screen full of data to
be displayed and then appear to wait for user input. In many cases,
data is still being downloaded to the client. Careful thought needs to
be employed before granting ODBC access to large tables on the
server.
Using dynamic substitution parameters speeds up your application,
if you are writing your own SQL to do multi-row inserts or updates.
In general, ODBCLink/SE will not complete any request faster than
ISQL would, and could be slower due to network overhead.