Re: how to migrate database from FileMaker to MySQL

From: BearItAll (spam_at_rassler.co.uk)
Date: 02/24/05 

Date: Thu, 24 Feb 2005 08:46:33 +0000

bird wrote:
> "BearItAll" <spam@rassler.co.uk> wrote:
>
>>bird wrote:
>>
>>>Hi,
>>>
>>>Does anyone have experience on migrating a database from FileMaker to
>
> MySQL?
>
>>>I have read some web pages and got lots of help on this topic. For
>
> example,
>
>>>this page:
>>>
>
> http://dev.mysql.com/tech-resources/articles/filemaker_mysql_whitepaper/file
>
>>>maker_to_mysql_whitepaper01.htm
>>>
>>>It seems to me the ActivePerl has to be installed on the same machine
>
> that
>
>>>FileMaker resides. But, for whatever reason I have to install the
>
> ActivePerl
>
>>>on a machine other than the one having FileMaker. Does this separation
>>>prevent me from migrating the database?
>>>
>>>Does anyone know a better way to do this task?
>>>
>>>thank you in advance,
>>>Kejun
>>>
>>>
>>
>>phew, you have a big job ahead of you going by what it says in that link.
>>
>>I don't know Filemaker, except what I have just read, and that suggests
>>that even with the migration tool you would have to do a great deal of
>>preperation before you ran it.
>>
>>Can I suggest a migration path that leaves the current database intact
>>while you prepare a place to receive it. I have to assume you have some
>>programming skills for this, could be on your linux or on your MS
>>machine. Also, they are glareing ommisions, simply because I do not know
>> Filemaker's way of storing functions and table links etc. Though I
>>suspect that they are pure SQL, so possibly a table with stored SQL
>>texts with markers for variables, because I remember when Filemaker
>>first came out it was developed by a team that came from the database
>>world of the time and that was the way we were all trying to go (yeah I
>>know, ideals and real life programming don't mix too well). But at least
>>I'm confident they would of stuck to the "data-access method-client"
>>model, where each is properly seperate. i.e any one part can be changed
>>without affecting the others.
>>
>>So all I can really do is provide food for thought.
>>
>>You get ODBC access with both mysql and Filemaker. So you can collect
>>table names and field names programatically from Filemaker, you have to
>>clean the names for use in mysql. At the same time you can collect field
>>types, be carefull on field matching.
>>
>>So here's a draft.
>>
>>1. Create the empty database in mysql.
>>2. Read Filemaker table names in your code. Clean them. Then create a
>>table matching table.
>>3. For each table read the field names, which also must be cleaned. And
>>the field types. Create a field matching table.
>>4. Have your code create the receiving tables.
>>
>> From that you should be able to see a route for copying the data via
>>your code.
>>
>
>
>>Then they is the client side to sort out. But, as Filemaker can also use
>>external tables, it could link to the tables held in mysql (via odbc).
>>so that now you have a second phase situation, where your clients are
>>unchanged but the data is in the new location. That buys you yet more
>>time to write the new client code.
>>
>>
>>This is actually the sort of database work that can be the most
>>interesting. But I can only be sketchy because I don't know your
>>database or Filemaker very well.
>
>
> Thank you. I'm trying to help the graduate student office to do the job. (I
> won't get paid.) I've years experience with a few mainstream DBMSs, but
> unfortunately I don't have any with FileMaker. I guess it is something like
> Microsoft Acesss. The database itself isn't large. It shouldn't be altered
> during the migration since it's a production database.
>
>
> According to the outline shared on the mentioned web page, I think I know
> the basic steps to do the job. I only have one uncertain. That's if I can
> install ActivePerl on a separate machine. I cann't work on the production
> machine. I think I need to access FileMaker by ODBC, and I can access MySQL
> using whatever I like. They do plan to replicate the old program with a new
> one using the new MySQL database. I don't know who will write the program
> yet, but probably that's me because the MySQL+PHP solution is my idea.
> Really sad!
>
>

Oh really Bird, haven't you learned to keep quiet at meetings?!? ITers
and Programmiers always talk themselves into more work in meetings. I
used to practice by putting duc tape across my mouth. In fact I got
quite addicted to it.

Relevant Pages

  • Re: Filemaker/Access Linux alternative
    ... For your database, you should consider MySql. ... of that for Linux. ... > Filemaker and my partner access. ...
    (comp.os.linux.misc)
  • Re: how to migrate database from FileMaker to MySQL
    ... or extra fields in the FileMaker database ... > one using the new MySQL database. ... or XML) and then import that into the new SQL database. ...
    (alt.os.linux.redhat)
  • Re: Converting a FM9 table to MySQL View with minimal effort
    ... MySQL view in FM, and reconnecting all the table occurrences or is there ... the tables and fields and writing a batch file to create a similar SQL ... strongly used type of field in FileMaker called calculations. ... have to be included in the application layer of your new database. ...
    (comp.databases.filemaker)
  • Re: Converting a FM9 table to MySQL View with minimal effort
    ... MySQL view in FM, and reconnecting all the table occurrences or is there ... strongly used type of field in FileMaker called calculations. ... have to be included in the application layer of your new database. ... use that data that is in the exact same order as the current FM table? ...
    (comp.databases.filemaker)
  • A Shot in the Dark - mysql C++ api
    ... I don't know if anyone knows anything about programming C++ to do mysql ... database manipulation, but here it goes anyway ... ... bunch to use to manipulate databases), a C api and a java api ... ...
    (comp.lang.cpp)