The issue is with how Filemaker datasources are managed, and a difference in a couple of characters in the file structure (I believe it was a high-ascii vs low-ascii character problem) that requires the conversion. If there aren't too many TAF's to do, simply open them in the new editor and reselect the datasource and resave the file. There is a way to do a search-and-replace on large numbers of files - I've pasted in the bit from Phil's presentation on it. If you have a large number of TAF's that need converting, this would be good to experiment with (with a backup, of course...)
Good luck - and keep us posted.
Jason
Excerpt here:
------------
The fastest and easiest way to correct the problem with the character encoding is to open the TAF/TCF files that were created on OS 9 in a text editor and:
replace:
<Host><![CDATA[�]]></Host>
with
<Host><![CDATA[#]]></Host>
To find the datasource section search for <!--Data sources--> in the taf file.
keep a backup
-----------
On Wednesday, October 1, 2003, at 03:55 PM, Chuck Leavens wrote:
--I am starting to build new tafs and the first test of a DB search taf works. Next is testing a data entry taf.
Post args are working on the new box. YES! Sure is disappointing that T2K tafs won't run under WT5. Sure wish there was a converter.
--
Thanks,
Chuck
Chuck Leavens Director of Engineering and IT Management
WDUQ-FM Duquesne University Pittsburgh PA 15282
412-396-5508 Direct
[EMAIL PROTECTED]
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
____________________________________________________________________
Jason Pamental, President [EMAIL PROTECTED]
Bathysphere Digital Media Services, Inc. http://bathyspheredms.com
____________________________________________________________________
Tel: 401.490.6830 Fax: 401.490.6831
________________________________________
A North American Distributor for Witango (http://www.witango.us)
Rapid Web Application Development - XML Execution Engine
