MY Eyes have been opened

ryan at bulldogsoftware.com ryan at bulldogsoftware.com
Thu Feb 9 10:55:05 PST 2006


On Thu, Feb 09, 2006 at 12:51:19PM -0500, Robert Haussmann said:

> > 	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.

But if there were an ODBC driver for filePro there would be *something*
running, that is, the driver itself within the ODBC manager. So whether or
not the thing that "is running" is some filePro daemon, or the driver
itself, doesn't really matter. 

You could write (theoretically anyhow) an ODBC driver for filePro that does
it all, or you could write a simple protocol driver that knows how to talk
to a filePro daemon, which you would also have to write. The data sources
you mentioned are all covered by Microsoft's proprietary drivers and they
threw in text files as a bonus. By that same token, MyODBC only knows how
to talk to MySQL servers. 


-- 
Ryan Powers
Bulldog Software, Inc.
http://www.bulldogsoftware.com
-------------------------------------------------------------------------------


More information about the Filepro-list mailing list