Filemaker Output

Hi Experts,

I have a client that has an old Filemaker 12 database, we are replacing it with an SQL system. We need some kind of export of all the data inside the old one. The person who created it is not cooperating, and we're having trouble finding anyone that knows enough about Filemaker to do so.  We have an account for the DB with admin rights, but no idea where to start. We don't really care what format the output is in, as long as it's something we can read to CSV or Excel and prepare for import into the new system.

Is there some kind of script or function we can run to export ALL the tables to some friendlier format?

Thanks!
LVL 1
Myles CardiffDeveloperAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

North2AlaskaSenior EngineerCommented:
I can understand the feelings of the previous owner, but what you are asking for is not unreasonable.   That said, yes you can export the data.  Can you get to the relationship graph?  You need to start there.
0
Will LovingPresident, Dedication Technologies, Inc.Commented:
You can probably manually export all records from each table and if this is a one-time export then it's probably faster than scripting it. You need a list of all tables which you can get from File -> Manage -> Database -> Table tab.  If you don't have access to that (which means you don't have full admin rights or what FileMaker calls a "Full Access" privilege set), then try the Layouts dialog (File -> Manage -> Layouts).

Each layout is associated with a table so open a layout for each table you want to export, use "Show All Records" from the Records menu or Status bar at the top, and then File -> Export...  I would recommend using the "Merge" format which is simply a CSV export with a header record containing the field names. Having the field names will be of great help as you do your conversion.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Myles CardiffDeveloperAuthor Commented:
Thank you for your responses.

Will, we've started an export of the first table as you suggested, So this will work, but it's pretty slow. The current table has about 8000 records, and it does about 1 per second. There are some other tables in the database that we know have 80,000+ rows. My guess is that it's slow because we're doing this from a client machine, Are you aware of any tools that could perform directly from the server side? Like you would with SQL Server Management Studio?

Thanks!
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Will LovingPresident, Dedication Technologies, Inc.Commented:
Working from a client machine using hosted files will definitely make the export slower. The best speed will be from having a copy of the files open locally in FM Pro as opposed to connecting to a server via "Open Remote..."

The other thing that will make the export slow is if you are exporting summary and calculation fields. Assuming you have access to File -> Manage -> Database you can look at each table and see the field types. There is no reason to export Summary fields at all as they are generally used for reporting and rely on other fields only. Also look for calculation fields that reference other tables. These may have been added for reporting, appearances, dialogs, etc. and are most likely unnecessary as they also reference other fields and do not contain raw data. Global fields also do not need to be exported and container fields will not give you anything of value in a CSV export.

If you don't have access to the full field list you might be able to determine which fields are summary and calculation based on naming convention, but only if the original developer choose to use one. One convention is to include a suffix such as "_s" for summary fields or "_c" for calculation fields.
0
Myles CardiffDeveloperAuthor Commented:
Ok, great. This really helps!

Thank you!
0
North2AlaskaSenior EngineerCommented:
If you have full access, you could set it up as and ODBC source and point a SQL tool at it to do the extract.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
FileMaker Pro

From novice to tech pro — start learning today.