I have discovered if I create the odbc registry keys specifying an alternative name for
the DBISAM 4 ODBC driver I can still connect to the DBIsam server by specifying the
alternative driver name in my connection string. Doing this would enable me to
differentiate between the installation of the driver for my app and any other installation
of the DB Isam driver on the client computer. Is this ok under the license agreement?

Also, on first installation does dbodbc.dll need to be registered using regsvr32.exe or is
creating the registry keys sufficient?

Steve,

<< I have discovered if I create the odbc registry keys specifying an
alternative name for the DBISAM 4 ODBC driver I can still connect to the
DBIsam server by specifying the alternative driver name in my connection
string. Doing this would enable me to differentiate between the installation
of the driver for my app and any other installation of the DB Isam driver on
the client computer. Is this ok under the license agreement? >>

Absolutely.  In fact, we encourage you to differentiate your distributed
ODBC driver from the "stock" driver.

<< Also, on first installation does dbodbc.dll need to be registered using
regsvr32.exe or is creating the registry keys sufficient? >>

The registry keys are sufficient - they're a direct path and that's all the
ODBC administrator needs.

--
Tim Young
Elevate Software
www.elevatesoft.com

<<Absolutely.  In fact, we encourage you to differentiate your distributed
ODBC driver from the "stock" driver.>>

Excellent, and is it ok to redistribute the 'Server Adminstration Utility' and the
'Database System Utility' to the end-user?

Steve,

<< Excellent, and is it ok to redistribute the 'Server Adminstration
Utility' and the 'Database System Utility' to the end-user? >>

Yep, no problem.

--
Tim Young
Elevate Software
www.elevatesoft.com