Sorry but I must disagree. I've done a few of these types of conversions myself and during my time with EveryWare I support many many customers who tried these types of conversions.
One of the worst things that you can do is to try to create a structure of a SQL database around what was used in FMP. I've seen users actually try to name their tables 'Layout_0' in an attempt to do this. I'm probably going to get flamed here but I'll say this again (and yes I do like FMP for what it is), FileMaker Pro is NOT a true SQL-style relational database. In most cases it will take just as much time if not more, to go in and change all the little things that need to be changed in your existing taf files then it would take to create new taf files using either builders or drag and drop from your datasource pallet. I've found the best method is to create new taf files that hit a new ODBC datasource that has got a proper structure. Then copy most (whatever is usable) of the HTML from your existing taf files, making the necessary changes to the <@COLUMN> tags. I'd be happy to provide more information if you need it. Hope this helps, Steve Smith Skadt Information Solutions Office: (519) 624-4388 GTA: (416) 606-3885 Fax: (519) 624-3353 Cell: (416) 606-3885 Email: [EMAIL PROTECTED] Web: http://www.skadt.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of T.J. Roberts Sent: August 8, 2002 12:47 PM To: Multiple recipients of list witango-talk Subject: Re: Witango-Talk: FMP to SQL The key is to make sure the field architectures match, and then you will save lots of time. The beauty of ODBC is that if the datasources have like architectures, then all that will be needed is to re-Set the Datasource. I have noticed that sometimes an operation may need to be re-generated which is not that big a deal, that is, re-creating the Search query or Insert operation and deleting the old one. >What and how much code will have to be rewritten/reworked? Did you ever >consider just rewriting the entire app? Or are their time-saving benefits to >reworking your existing FMP code? > >Chris > > > > > Yes, we have. Its a decent project to do the work, but the speed > > throughput you get from moving to SQL Server makes it worth it. We > > dumped Tango for Filemaker Pro years ago because of its slowness. > > > > > > > > Regards, > > > > T.J. Roberts > > Organize-it Software, Inc. > > > > "...a picture is worth a 1000 words!" > > > > http://www.Organize-it.com > > http://hsdm.Organize-it.com > > http://www.KindestCare.com > > http://www.KindestFood.com > > http://tampa.Organize-it.com > > http://medss.Organize-it.com > > http://va.Organize-it.com > > http://dms.Organize-it.com > > >> Has anyone ever tried to convert a Tango app from FileMaker to SQL? > >> > >> Chris > >> > >> -- > >> > >> Chris Millet > >> Millet Group > >> 3900 Elm Street > >> Dallas, TX 75226 > >> 214.761.1166.16 > >________________________________________________________________________ >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 ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
