Jump to content
Salesforce and other SMB Solutions are coming soon. ×

FMP 7 conversion help please


dvandam

Recommended Posts

I am trying to convert our application to version 7. It is a relational application with about 20 files. We have about 300 users of our application in different offices all over the world and some of them are starting to go to FMP 7 so I need to be able to help them with their conversions. I tried to convert our copy of the application here and would like somebody to give me some input on what is happening. For example, I have some scripts that basically just open another file in a specic layout and they are converted as Members (which is what I expected) but sometimes it's Members 4 and sometimes it's members 7, etc. and then when the script runs it says it can't find the file.

 

So then I looked at File References and there's files refered to on the C drive, E drive (which I don't even have) and files referred to at IP addresses that I don't even know what they are.

 

Anyone got any ideas how I sort this thing out or should I start over or what? Thanks.

Link to comment
Share on other sites

You should get familiar with the FM7 Foundations and Migration Methodologies tech brief on filemaker.com. This addresses many conversion issues, including the file references problem you have already found.

Link to comment
Share on other sites

Okay I read it. Now what. It tells me to buy some 3rd party product to fix my file references before I convert. And what do I tell this member of ours who is 500 miles away who just converted and now it runs so slow it's almost unusable plus he gets "file not found" errors all over the place. This is not looking good right now.

Link to comment
Share on other sites

Although references can be fixed post-conversion, it is much easier to fix them before conversion with MetadataMagic's File Reference Fixer.

 

If your members have already been using the converted solution, then you'll probably need to figure out how to fix the file references manually, so you can give instructions to your members.

 

You might also convert and optimize clones of your master, adding import scripts so you can send it to anyone else that needs to migrate soon. They would convert their current files, then run an import script to move the data from their old version to the new. If they have customized their files, however, they may have trouble.

Link to comment
Share on other sites

I don't think most of our members are going to want to pay the $300 to fix their file references before converting.

 

Maybe you could give me some feedback on what I think is the way to correct the file reference issue. I think that editing the file path the file referencing window to point to the file in the folder might do the trick. I realize that I would then have multiple definitions for the same file like companies, companies 3, companies 5, companies 6, etc. but if they all point to the same file I think it will work. If I delete them, I'm going to have to go through all the relationships and scripts to find the items and redo them. I realize that this is not maybe the most efficient way to do it but might work. Thanks.

Link to comment
Share on other sites

Why not siimply stay with FMP 6.0? I have and found no problem with users when I explained the problems attendant to the conversion process.

 

Tom

Link to comment
Share on other sites

[ QUOTE ]

I don't think most of our members are going to want to pay the $300 to fix their file references before converting.

 

[/ QUOTE ]

 

If it is a large solution, then $300 will be cheaper than the time needed to do it manually.

 

[ QUOTE ]

I think that editing the file path the file referencing window to point to the file in the folder might do the trick. I realize that I would then have multiple definitions for the same file like companies, companies 3, companies 5, companies 6, etc. but if they all point to the same file I think it will work. If I delete them, I'm going to have to go through all the relationships and scripts to find the items and redo them.

 

[/ QUOTE ]

 

It sounds like you have a handle on the issues. You can simply reset the incorrect paths to point to the right file. This will make all your relationships and scripts work, but creates a little confusion when setting file references in a table occurance or external script. Or you can eliminate the duplicates, but this requires a lot of work to clean up.

 

The File Reference Fixer consolidates file references to the correct local (or remote) files, and it only takes a few minutes.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.



×
×
  • Create New...

Important Information

Terms of Use