fileProODBC (was Re: OT: Filemaker 8)

[Tyler Style]

Kenneth Brody wrote:
  > And, what you still haven't comprehended, is that ODBC has two
> completely distinct and separate parts -- clients and servers.
> The only thing that these two parts have in common is that
> clients use the ODBC protocol to talk to servers to get them
> to do things for them, exactly like a web browser (aka "http
> client") and a web server (aka "http server") have nothing in
> common except for the http protocol they use to communicate.
> 
> fileProODBC is an ODBC client.  There is currently no filePro
> ODBC server available from fPTech.  (And note that, unlike some
> claims to the contrary, the client has read/write capability.)
> 

Yup.  We have been talking about clients and servers.  Totally agreed. 
As I keep pointing out, filePro is primarily a database backend, a 
server.  I don't think most people think of it as being a client 
development platform like VB, as the only thing that the fP app 
interfaces provided are generally used for is accessing fP data.  The 
vast majority of database backends (ie, servers) have ODBC connectivity 
for client applications to use to connect to them and manipulate data. 
A developer would thus expect to have such available to him for 
connecting to a filePro datasource, especially given that fP has been 
around for yonks and yonks.  It doesn't, which surprises people, 
especially when they hear that filePro has ODBC.  Because they think of 
filePro as a database server.  Not a client.  And database servers are 
generally accessible via ODBC.

I understand that fP has a client ODBC connectivity only.  That's what 
I've been complaining about.  That's what fpTech's sales told me.  No 
misunderstanding there.  And it's a serious lack for any mature db product.

Tyler