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
