Bulldog ODBC for filePro

[ryanx at indy.rr.com]

On Tue, Mar 08, 2005 at 11:53:52PM -0500, Jay R. Ashworth said:

> What we've been asking for for ages is an ODBC server (why can't
> *anyone* just *call* them clients and servers, so we don't have to
> guess?) implementation that will let live clients talk to active
> filePro data file sets.  

Well, thats true, Jay. A full-fledged ODBC 3.51 conformant server it
is not, and I think the price reflects that. But that is not to say
that it will not evolve into one through future development. 

And it is neither a client nor server. I think the correct term would
be "ODBC bridge".

> You didn't read my other reply, I think.  As near as I can determine,
> "this going over well" is defined as "letting a whole bunch of filePro
> sites pull their data out and move it over to 'something easier to use'".

How about move it over to something where it can be seen? Building a
bridge between filePro and Access (initiated by Access) is the
purpose. Its a tool, not a call for a mass exodus. Just the other day
Jose was inquiring about getting filePro data into MySQL. With my
product he can do this in two steps: import into Access, then export
via MyODBC.

Certainly there are many different ways to get filePro data out onto
the internet or whatnot. This is just makes it easier. But that does
not in itself render filePro obsolete.

What is harming filePro more than anything is the lack of tools to
make it easier to work with.

> And, as I say: I don't see anything that explains how Ryan views his
> roadmap for the product.  He may well plan to make it into a full
> server-side implementation.  But I can't tell.  Do you really think it
> wouldn't have been a good idea to put that in the posting here, even if

Its all tentative. If there is enough interest, there will be further
development.

-- 
Ryan
-------------------------------------------------------------------------------