FW: re - fileProODBC (was Re: OT: Filemaker 8) -aka: more worthlessrambling on

[Tips]

If filepro on a Unix server serving data to 32 user terminals isn't a
server, then I don't know what is...  I absolutely agree that if filepro is
ran on Unix, it by all means is a Server.  Now if it is on a dos/windows
box, then I guess it could be viewed as a proprietary single/network
non-server application, but not so when running on SCO, Linux and the other
"SERVER" os'es...

My 32 users all are running my filepro apps on Windows using Anzio.  They
also each have Office 2000/2003 installed and it plays a big part in their
day2day business.  Now, if these users cannot easily connect their Excel
application to what should be the "served" filepro data, then what use is
it?

Stanley



 

-----Original Message-----
From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com] On Behalf Of Christopher
Yerry
Sent: Tuesday, February 07, 2006 9:41 AM
To: tyler.style at gmail.com; List Filepro
Subject: re - fileProODBC (was Re: OT: Filemaker 8) -aka: more
worthlessrambling on

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    
            AMEN !! 
                     Well said

As I have said (many times) before - filePro is a flat
file. It isn't hard to add to the table and then re
index the data. Just takes some coding (we are
programmers after all) ugly but very straight forward.

To Nancy - we don't use ODBC any more; yes it is old -
to everyone that writes me that we still do but don't
know it - we still use interrupt 21 also but we have
upgraded it a bit. 

I like filePro I always have but there's' a reason I
get 50 .NET jobs to one filePro - It used to be the
only game in town !!!!


Christopher Yerry
pres CM Software

PS - can we get rid of these ugly record locks - and
file locks they dont work at all on the web !!!!!

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list