Does anyone have any experience moving a MS Access 2000 database to Filemaker Pro 7? I was given a database in MS Access and can access it on a PC but would like to move it into Filemaker Pro 7 so I can use it on my mac. I cannot stand using Access if I can help it.
I see there is FmPro Migrator and it can do the migration but it states "FmPro Migrator for MacOS X generates migration scripts which are then run on VirtualPC or Windows to complete the migration process." Has anyone used this application? I am not sure if I do the migration on a PC (which only has access) or on my mac (which does not have VirtualPC) and how you are suppose to use Windows to finish the migration if it is suppose to be for OSX?
I've yet to see anything that will cleanly do this. They are very different beasts, especially in the scripting part of things. As for that migrator program I've watched it shred TONS of data, it's not to be trusted IMHO.
I used to be FSA (FileMaker Solution Alliance) but gave it up cause of...FMP issues.
I haven't heard of anything, but I agree with you on the Access part. It's horrible, and is taken as fact in the FMP community.
My suggestion is to export your tables to comma or tab delimited, then import into FMP. This will only give you tables, so you will have to build the logic on top of that in FMP. This is where FMP differs from other db's as if you did it in MySQL, all logic would be external from the tables. I develop using a middleware that reaches into SQL db's.
Thanks for the info. Looks like there is no easy way other than exporting the info into FM and rebuilding. Bummer but I guess I can use this opportunity to customize the database for my own use And for now I will be stuck with working on a PC and using Access uggh
On a related note: it's always said in Mac circles that MS Office for Mac doesn't include a version of Access due to Microsoft wickedness.
I read somewhere that this isn't so - MS tried sincerely to port Access to OS 9 and failed. Apparently it's so dependant on the Intel architecture that it can't be done in any practical time frame. Maybe this will change when the new Mac-intels come on line. Oh, goody! Access for Mac at last!
__________________ "I don't know the key to success, but the key to failure is trying to please everybody."
- Bill Cosby
On a related note: it's always said in Mac circles that MS Office for Mac doesn't include a version of Access due to Microsoft wickedness.
I read somewhere that this isn't so - MS tried sincerely to port Access to OS 9 and failed. Apparently it's so dependant on the Intel architecture that it can't be done in any practical time frame. Maybe this will change when the new Mac-intels come on line. Oh, goody! Access for Mac at last!
Really? That's very interesting considering a more powerful and more sophisticated MS database (FoxPro) ran on the Mac platform before MS killed it. I still have it...burried in my garage someplace. LOL!
Access is crap. A lot of better solutions out there, FM being one of them, but I see where you're going with this. If it comes with Office for Mac, fine...but I won't be buying a stand-alone version just to play nice with some crappy Access solutions. I'd rather see a FileMaker compatibility layer for Access that works seamlessly.
__________________
••••••••••••••••••••••••••••••••••••••••••••••••
Please help fight Cancer -Donate or volunteer to the Canadian Cancer Society
--------------- MOΛΩN ΛABE
Considering how crappy Access is, it does not suprize me that they could not port it. Hmm I liked having no access to Access on the mac, it is a good reason to switch over to FMP.
Not sure I would like the idea of being able to use Access on my mac. I find the more I use my mac, the more I try to move away from Windows products since they become annoying. Switched from Entourage to Mail, Powerpoint to Keynote, and now thinking of switching from Word to Mellel. A life with minimal Windows contact sounds lovely to me
Really? That's very interesting considering a more powerful and more sophisticated MS database (FoxPro) ran on the Mac platform before MS killed it. I still have it...burried in my garage someplace. LOL!
Access is crap. A lot of better solutions out there, FM being one of them, but I see where you're going with this. If it comes with Office for Mac, fine...but I won't be buying a stand-alone version just to play nice with some crappy Access solutions. I'd rather see a FileMaker compatibility layer for Access that works seamlessly.
For occasional use, Access works OK within Virtual PC.
I'm a big fan of FileMaker myself, but Access is so widespread that many of us have to deal with it sometimes.
It's hard to see how MS would benefit from such a compatibility layer, and they're not noted for altruism.
__________________ "I don't know the key to success, but the key to failure is trying to please everybody."
- Bill Cosby
__________________
••••••••••••••••••••••••••••••••••••••••••••••••
Please help fight Cancer -Donate or volunteer to the Canadian Cancer Society
--------------- MOΛΩN ΛABE
Hiya.
My suggestion is to export your tables to comma or tab delimited, then import into FMP. This will only give you tables, so you will have to build the logic on top of that in FMP. This is where FMP differs from other db's as if you did it in MySQL, all logic would be external from the tables. I develop using a middleware that reaches into SQL db's.
Good luck.
Further on this, if you export your tables in "Merge" format, which basically has the names of the fields as the first record of the export and then take each table in turn and drop it on the open FMP7 Icon, you will create a file for each of the tables with the field names already defined (They will probably all be of type text, but that can be changed).
From there you will have to make an executive decision as to develop as a multi file, multi table program, a la FMP 2 through to 6, or further collapse the files through to a single file, multi table program.
You will have to rebuild the logic and the relationships.
And for now I will be stuck with working on a PC and using Access uggh 
Linear Mode
