Jump to content

Importing new records from mySQL via ODBC

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

Recommended Posts

I've tried this post in another forum but got little response. Maybe I'll have more luck here.

I have a Filemaker database set up to mimic a mySQL database. In order to initially populate the FM db, I did File > Import Records > ODBC Source and grabbed everything from the mySQL db without a hitch.

Now I want to be able to use ScriptMaker to retrieve new records from the mySQL db from time to time (say, whenever the FM db is opened up). Executing the script when the file is opened is no problem.... importing the new records is!

I've set up a script that runs Execute SQL to select the data from mySQL and it appears to run ok except that none of the records are actually imported into the FM db. If I set up the script to run Import Records instead of Execuste SQL, I can import from only a file, not an ODBC source. Lastly, if I manually run Import Records > ODBC Source again, I get all of the records imported from mySQL again, not just the new ones.

I'm fairly new to FM so if I'm overlooking the obvious please let me know! But if you could help me out I would also appreciate it...



Link to comment
Share on other sites

I'm not too good with mySQL but I have an idea.

I would make a new table in your mySQL that is just all the new records thta need to be imported. Then have FM import that table (save the import and you can do it automaticly in a script.) and then some how get mysql to purge the new table for next time.

Link to comment
Share on other sites

This topic is 7864 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.