Actually, I don't think it should be that difficult -- as long as you didn't
rely on FMP for things like calculations, etc. If you think about it, the
logic is already done, the rest is busy work. I found the
performance/reliability benefits of MySQL very much worth the effort.
Here are the steps that I went through on the conversion:
1) Open 'old' and 'new' apps side by side.
2) Create new queries by dragging/dropping (the "hardest" part)
3) Copy/paste results html from old to new
4) Search and replace "Layout_0" with name of table ie: <@column
layout_0.fieldname> --> <@column tablename.fieldname>
5) Drag and drop additional actions (mail, control, etc) from old to new,
they should convert seamlessly
Depending on how you built your app, there could be a few additional steps,
but this should be the bulk of it.
Hope this helps.
Chris
> Von: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Organisation: SoftDes GmbH
> Antworten an: [EMAIL PROTECTED]
> Datum: Wed, 26 Feb 2003 19:24:09 +0100
> An: <[EMAIL PROTECTED]>
> Betreff: Re: Witango-Talk: Converting FileMaker Databases to MySQL on MacOS X
>
> Sorry, I have forget to say, that we also must convert the Taf - Files and
> in the past I have read that it will be the best to make everything new
> :-(((
> So, maybe know a good and fast way to convert the taf files. The Apps. are
> writen on MacOS, but a way tat work on Windows will also be welcome !
>
> The data's are allready in the MySQL Database...
>
> regards
>
> Daniel
>
> ----- Original Message -----
> From: "Beverly Voth" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, February 26, 2003 7:04 PM
> Subject: Re: Witango-Talk: Converting FileMaker Databases to MySQL on MacOS
> X
>
>
>> Hello, [EMAIL PROTECTED] On 2/26/2003 6:56 PM +0100, you wrote in
>> whole or part:
>>> OS: Mac OS X (or Windows)
>>>
>>> Problem: How can we convert a FileMaker Database on a easy wav to MySQL ?
>>
>> Export as .mer (merge) format. This is .csv (comma-separated values) with
> the field names as the first record.
>>
>> *** You may get funky results if you have field names with anything other
> than alphanumeric characters. Spaces may convert to "_", for example. ***
>>
>> Beverly
>>
>> ________________________________________________________________________
>> 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
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
