Filemaker 6 ODBC is not any better than Filemaker 5.5 ODBC and that was a
big change from Filemaker 4.0 ODBC.
In my test cases for Filemaker ODBC it is too slow for a real website, if
you can connect Tango to the filemaker DSNs at all.( most of my ODBC selects
time out, inserts seem to work OK, and deletes don't seem to work at all).
For most connections of Filemaker to a web application on a PC it is best to
use the Web Companion which uses XML.
It is possible to create a TCF that acts like the search, insert, and delete
requests from Tango to talk to Filemaker in XML.
The ODBC connections seem to work best for connecting to and from a SQL
server, Excel, and other more simple ODBC requests. So it is possible to
move to a SQL backend, but keep your FileMaker forms and interface.
John W. Arnold
[EMAIL PROTECTED]
----- Original Message -----
From: "Kent Swisher" <[EMAIL PROTECTED]>
To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]>
Sent: Thursday, September 26, 2002 4:05 PM
Subject: Witango-Talk: Filemaker 6 ODBC
> We are running wiTango 2000 on Macs using Filemaker 4. The powers that
> be keep trying to get rid of macs. They have asked me again why we
> cannot scrap Macs and go to PCs.
>
> Can anybody tell me if the ODBC capability of Filemaker 6 is good/fast
> enough to run a PC/wiTango/filemaker solution on a PC webserver? Moving
> to a "real" SQL database would be nice but would mean creating all the
> administrative user interfaces currently in filemaker from scratch.
>
> -> Kent Swisher Eng Services Supervisor
> -> Alcatel USA Application Support Engineer
> -> Wireline Access Products Eng Srvcs Content Mgr/Webmaster
> -> Petaluma, CA [EMAIL PROTECTED]
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
>
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
