Kent,
There will be a few steps to convert the file. All the steps can be
done with a global find and replace of strings with a text editor
like TextWrangler on OS X or TextPad on Windows. You need to convert
the databases with FileMaker first. Then remove the spaces from the
table names if there are any. The Tables are what you will reference
in the taf file not the Layouts. Also note down what the layout name
was and what table it is mapped to from within FileMaker.
Before you start make a backup of all your files first.
1. Remove the space from the datasource names. Just a precaution.
e.g.
Look for DSID="Telephone Directory" and replace it with
DSID="TelephoneDirectory"
Look for <DSN>Telephone Directory</DSN> and replace it with
<DSN>TelephoneDirectory</DSN>
2. Change the data source type to ODBC:
Look for <DSType>FileMaker</DSType> and replace with <DSType>ODBC</
DSType>
Look for <Host>´</Host> and replace with <Host></Host>
Look for <Host>#</Host> and replace with <Host></Host>
3. Convert Layouts to the table names used in FM8
Look for <TableName>THE LAYOUT NAME</TableName> and replace with
<TableName>PUT THE FM8.x TABLE NAME HERE</TableName>
4. Record_ID is not exposed through the ODBC interface. It is now
ROWID.
Look for record_id and replace it with ROWID.
You should now be able to use the taf files with a FM 8 database
through the xDBC interface. You can also use the JDBC driver by
changing <DSType>ODBC</DSType> to <DSType>JDBC</DSType> in step 2 above.
Regards
Witango Support
On 09/12/2006, at 9:28 AM, Kent Swisher wrote:
Nice to be back on the list after several years absence.
I am converting a number of applications from FM4/T2000 all on
MacOS9 to FMSA8/Witango 5.5 all on WinServer2003 (ODBC). Filemaker
has a lot of good info on the database conversions from 4 to 7/8.
Not doing so good finding info on Witango side.
In a pre-sales email directly with Phil Wade, he said:
“We have a simple procedure to convert taf files that were based on
FM 5/6 connectivity to xDBC based taf files.”
Unfortunately, Phil never got back to me when I requested a copy of
his procedure.
Have figured out a process myself. First TAF conversion went
pretty well. Search and replace Layout_0, scrub actions and search
criteria for layout_0 references. Change data sources in actions.
Create custom column in search criteria (upper()) to deal with new
case sensitivity. Check tags that have modified behavior since T2K
for compatibility. Only 50 more TAFs to go…
Questions:
Would help to see a list of issues/gotchas that others have
discovered when doing similar conversions to see what I missed or
have not encountered yet. Anybody have such a list?
Can any of you provide Phil’s procedure?
Also seen mentioned when searching the list archives is reference
to Phil’s presentation on T2000 to Witango 5.0 Mac conversion
issues (high-ascii vs low-ascii character problem? and Yen
character?). Do these T2k Mac to Wt5 Mac problems also apply to
Mac to PC conversions?
Is there a way to make FMSA8 odbc case insensitive by default?
Know about the custom column in search criteria (upper()) to deal
with new case sensitivity. Would be easier if could ignore case
globally.
-> Kent Swisher Engineering Services
-> Alcatel-Lucent Application Support Engineer
-> Wireline Access Products [EMAIL PROTECTED]
-> Petaluma, CA 707-792-7116
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
