I have used it in the past. The Filemaker application MUST be open as GUI on the target server for it to interact as a web data source.
It does ok with simple queries, slows down with large queries and sorting. It ques request one at a time - linear But, if the client already has Filemaker set up as an internal database ( which it does very well ) it's a breeze to web-enable out of the box. So, for low traffic, keep Filemaker. Here is a thought.. if the client wants to keep Filemaker internally and you can use SQL Server, set up a DTS to extract data out of Filemaker into SQL Server and then use ColdFusion. Dave ----- Original Message ----- From: "Kodjo Ackah" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, September 24, 2002 10:00 AM Subject: Filemaker faults to win a bid for using CF > I need some strong points on the shortcomings of filemaker to win a bid > to use CF. > Any bright ideas? > > Kodjo Ackah > Principal Consultant > Concrete Media Ltd > 32 Great Sutton Street > Clerkenwell > London, EC1V 0DX > > Tel:+44 (0)20 7251 8090 > Fax: +44 (0)20 7251 8780 > Mobile: +44 (0)7748 79 1038 > > Office Location: > http://www.streetmap.co.uk/streetmap.dll?G2M?X=531852&Y=182204&A=Y&Z=1 > > > > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
