If we have an FM5 application already in use and want to switch everything over to mySQL, is PHP capable of accessing an FM5 database? When we try to come up with it (because we're trying to figure out how to export all the fields in multiple FM5 datasets), mySQL reports "Cannot find structure". Please note: We are unable to export using FM5, just won't do it because FM5 crashes right after a full export is requested. Tried 150 times. So now we're trying a back-door approach.

I think FM5 is so ancient, this is doomed. But what do you good people think? I think if we could get in with PHP talking to the FM5 dataset, we might be able to set up a program to strip out the data, save it to a mySQL file-type and move on.

Doomed?

Thanks.

H

If this is a one time thing - just to migrate to mySQL - you probably would be better served figuring out why FileMaker's crashing on export, rather than attempting to integrate with PHP just for exporting purposes.

I would guess there's corruption in the file.

Can you export partial datasets from any of the files (e.g. a single record)?

Have you tried running a Recover process and then exporting from the Recovered file?

OK Colin - thanks for your reply.

Yes, we've tried every thing we know how to to "Recover" using FM's recovery module. You name it, we've done it. We have a professional programmer helping us with the new database and he's building a new app from the ground up. Our FM setup just isn't what we need for instance, can't access it remotely. And a bunch of other issues I won't bore the group with. We think migrating is the best (and probably only) option. Of course FM staff tell us when we call, "We can't support that version - too old" and our non-profit cannot afford an FM upgrade.

I just wanted to know IF anyone knows IF mySQL can address a FM database?

I wasn't arguing against migration.

I guess my point is, if you can't export from FileMaker's built in export routines, you might not be able to get it out using any other method, since whatever you use may trip up on the corrupt record(s).

You say you tried everything...did you try my suggestion to export a single record? There was a point to that test.

If you can export partial datasets, but not a full dataset, then you have one or more corrupt records, and we can try to offer methods for removing them.

That said:

Look here

OK, I see your point.

The FM5 DB is made up of seven tables, like any good normalized DB should be. If I try to export just one record, incorporating all 7 related tables - crash. If I move past the first to just the next record and export that one - crash. And, if I focus on just the 250th record, export all - crash. If I take the entire database, well you know. BTW the error message is a standard Windows dialog,"File Maker 5 has enountered an error and needs to close. If you were doing any work, etc. etc".

However, through experiementation, the difference is, I can export one whole table (.fm5) at a time all the way through each table and come up with, for instance, seven .csv s. The .csv s do not list the field names across the top like I was hoping. But, luckily the single primary key in our application (Rec No) is exposed in all seven of them if I export to a "merge" (.mer) filetype per other instructions I've received here in the forums.

IMO, this particular install of FM is flumoxed. Could we re-install it? Did that already. No difference. The OS is WinXP_Pro fully patched.

So that's my story and I'm sticking with it. But, hey, I like the Migrator! Wonder if a trial version would get me where I need to be as a lot of demo-ware allows you to go so far. Would do best to call, because although they list a "free demo" there's no where to download it from even though they specify a "link" available to the "left".

I suppose I can call and ask. I really only need to use it ONCE!!!

"The .csv s do not list the field names across the top like I was hoping."

Field names are not part of the csv spec. However, the Merge file (.mer) is csv with field names in the first row.