Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

replacing fm data with mysql data without loosing table and field referencees


This topic is 6011 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Hi All,

Many apologies in advance, this is a bit long winded.

I work for a charity and we're in the process of moving fm data to mysql but we'll still need to carry on using fm for calculations, mailouts, etc.

So for example we had a table called 'memberships' in fm, I created a table with the same name in mysql and exported all the data to it. I then deleted the memberships table in fm and linked the external memberships table into fm via ODBC.

Naturally as soon as I deleted the fm memberships table all scripts and layout objects also lost the reference to it and linking the mysql memberships table didn't rectify this problem either.

I managed to solve the problem with the scripts by reimporting them from a backup fm database, but I don't know how to solve the same problem with the layout objects.

Is there a way to delete or rename tables/fields in fm without affecting the scripts and objects referring to them?

Many thanks in advance, I would really appreciate any help. We have a lot of tables to migrate this way!

Marcsi

Posted

This is untested and may not work, but you can try not to Delete the old Table Occurrence, but rather repoint it to reference the mySQL TO instead of the old FileMaker table. If on chance some of it does work, you will probably still have to clean up a lot of stuff, but maybe not lose all of it.

Posted

Hi John, thanks very much for the response. How do I repoint a table? I couldn't find an option for this yet.

many thanks again,

Mariann

Posted

Hi Mariann,

John probably won't mind if I answer this one, since I believe I learned the technique from him ... :)

Always back up first, then ... find your table occurrence in the graph. Double click it to bring up the Specify Table window. Click the Data Source dropdown and re-select the new source. Be sure the key fields are pointed properly before exiting out of Manage Databases.

LaRetta :wink2:

Posted

Hi Laretta thanks very much for the quick response! I'll give this a go as soon as I get to work. Just one question: when you say be sure to point the key fields properly...do you mean the fields that are foreign keys or primary keys should be linked to the appropriate tables or did you mean something else?

Many thanks again,

Marcsi

Posted (edited)

Yes, I meant if there were pre-existing keys and you change data sources AND the fields aren't in the same order in the new data source as was in the old, the primary and foreign keys will not line up any more. So make sure they are again mated before closing out of your graph. :wink2:

Oh. And keep in mind that, if the fields aren't in same order ( old source compared to new ) that any imports based upon the original data source will probably go mis-map.

Edited by Guest

This topic is 6011 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.