Converting a FM9 table to MySQL View with minimal effort

d-42 wrote:
> On Aug 20, 12:01 pm, Micah wrote:
>
>> Because I want to work with normalized data in PHP. To convert our FM
>> system to a normalized data structure will take at least 9 months.
>
>> I
>> can normalize the data and put a new front end on it in 4 months using
>> MySQL while still presenting a denormalized view to FM for integration.
>
>
> Frankly, I can't really envision a scenario where taking an FM
> database, converting it to MySQL, and then exposing the tables back to
> FM from MySQL as denormalized views would be preferable or indeed,
> faster than just cleaning cleaning up the structure in filemaker.
>
> -regards,
> Dave
>

I wanted to avoid an immediate overhaul of the FM system because a
rewrite would take years. I thought if I can present the same table
name, relationships, and data it would integrate with the current
system, but I realize that is not possible now. I am looking into other
options.

Thanks,
Micah

Micah wrote:
> d-42 wrote:
>> On Aug 20, 12:01 pm, Micah wrote:
>>
>>> Because I want to work with normalized data in PHP. To convert our FM
>>> system to a normalized data structure will take at least 9 months.
>>> I
>>> can normalize the data and put a new front end on it in 4 months using
>>> MySQL while still presenting a denormalized view to FM for integration.
>>
>> Frankly, I can't really envision a scenario where taking an FM
>> database, converting it to MySQL, and then exposing the tables back to
>> FM from MySQL as denormalized views would be preferable or indeed,
>> faster than just cleaning cleaning up the structure in filemaker.
>>
>> -regards,
>> Dave
>>
>
> I wanted to avoid an immediate overhaul of the FM system because a
> rewrite would take years. I thought if I can present the same table
> name, relationships, and data it would integrate with the current
> system, but I realize that is not possible now. I am looking into other
> options.
>
> Thanks,
> Micah


I agree with Dave, rebuild the FM Database from scratch. Think of it as a
template for the input/data display requirements.


The 'de-normalised' bit: the 'de-noramalized' (i.e. the non-normailzed)
FM fields present on the layouts, can be be (generally) redefined to
use hopped relationships equivalents in the normalized tables... THere
goes the old FM structure...

Just out of curiosity, how may tables and fields are you dealing with?

Chris Brown wrote:
> Micah wrote:
>> d-42 wrote:
>>> On Aug 20, 12:01 pm, Micah wrote:
>>>
>>>> Because I want to work with normalized data in PHP. To convert our FM
>>>> system to a normalized data structure will take at least 9 months.
>>>> I
>>>> can normalize the data and put a new front end on it in 4 months using
>>>> MySQL while still presenting a denormalized view to FM for integration.
>>>
>>> Frankly, I can't really envision a scenario where taking an FM
>>> database, converting it to MySQL, and then exposing the tables back to
>>> FM from MySQL as denormalized views would be preferable or indeed,
>>> faster than just cleaning cleaning up the structure in filemaker.
>>>
>>> -regards,
>>> Dave
>>>
>>
>> I wanted to avoid an immediate overhaul of the FM system because a
>> rewrite would take years. I thought if I can present the same table
>> name, relationships, and data it would integrate with the current
>> system, but I realize that is not possible now. I am looking into other
>> options.
>>
>> Thanks,
>> Micah
>
>
> I agree with Dave, rebuild the FM Database from scratch. Think of it as a
> template for the input/data display requirements.
>
>
> The 'de-normalised' bit: the 'de-noramalized' (i.e. the non-normailzed)
> FM fields present on the layouts, can be be (generally) redefined to
> use hopped relationships equivalents in the normalized tables... THere
> goes the old FM structure...
>
> Just out of curiosity, how may tables and fields are you dealing with?

Over 100 tables and 1000 fields.

If you have this many tables/fields, it seems like FmPro Migrator might be
helpful. It will also convert the repeating fields if you have them in your
FileMaker database.

--

David Simpson
www.fmpromigrator.com
"Micah" wrote in message
news:48adf955$0$29596$9a6e19ea-at-news.newshosting.co m...
> Chris Brown wrote:
>> Micah wrote:
>>> d-42 wrote:
>>>> On Aug 20, 12:01 pm, Micah wrote:
>>>>
>>>>> Because I want to work with normalized data in PHP. To convert our FM
>>>>> system to a normalized data structure will take at least 9 months.
>>>>> I
>>>>> can normalize the data and put a new front end on it in 4 months using
>>>>> MySQL while still presenting a denormalized view to FM for
>>>>> integration.
>>>>
>>>> Frankly, I can't really envision a scenario where taking an FM
>>>> database, converting it to MySQL, and then exposing the tables back to
>>>> FM from MySQL as denormalized views would be preferable or indeed,
>>>> faster than just cleaning cleaning up the structure in filemaker.
>>>>
>>>> -regards,
>>>> Dave
>>>>
>>>
>>> I wanted to avoid an immediate overhaul of the FM system because a
>>> rewrite would take years. I thought if I can present the same table
>>> name, relationships, and data it would integrate with the current
>>> system, but I realize that is not possible now. I am looking into other
>>> options.
>>>
>>> Thanks,
>>> Micah
>>
>>
>> I agree with Dave, rebuild the FM Database from scratch. Think of it as a
>> template for the input/data display requirements.
>>
>>
>> The 'de-normalised' bit: the 'de-noramalized' (i.e. the non-normailzed)
>> FM fields present on the layouts, can be be (generally) redefined to
>> use hopped relationships equivalents in the normalized tables... THere
>> goes the old FM structure...
>>
>> Just out of curiosity, how may tables and fields are you dealing with?
>
> Over 100 tables and 1000 fields.