MY Eyes have been opened

[Robert Haussmann]

> 	With the client version, filePro requests a ODBC server
> (such as MySQL which is constantly running, waiting for a request)
> to read and write the MySQL records. A filePro ODBC server
> would have to run constantly and allow MySQL to read and
> write filePro's records.
> 

A data source does *not* have to be client/server to have an
associated ODBC driver that allows other software to read/write
to the data source.

Examples include:

Excel
Access
dbase
foxpro
text files

None of these have a server component running.  They are ODBC
drivers that allow non-client/server types of sources to be 
read/written.  I think this would be what 99% of developers 
asking for "ODBC server" really want.

That being said, there are software companies that sell "ODBC
framework" development kits for approx $10K.  These are royalty
free.  To provide ODBC-access to legacy data, you just need to
provide the "glue" between the ODBC framework and the underlying
data source (presumably handle record locking, read/write records,
etc.).  For anyone that is interested, one such example is (no
idea on the cost or licensing on this one; it's just the first
that comes up in google).

http://www.odbcsdk.com/products/openaccess/odbc_overview.asp

Bob Haussmann
Tabor Children's Services, Inc.