FM7 migration experience

[begreen]

We just migrated a fairly big db system over the weekend. Most things went pretty well. We did a sandbox test a couple weeks before, so we had a pretty good handle on what to expect. First surprise was that there were a ton of bad file refs that needed cleaning up. But we've come across a couple bugs too. One is with popup lists that refer to a value list formed by a related field in another db. In FM6 this is fast, in FM7 very slow. Temporary fix has been to change them to popup menus, but this is not as elegant.

Another thing we are seeing is with sub-scripts running from a master script in related dbs. In FM6 only the master script window stays visible, but in FM7 every related db that has a sub-script pops open. Very ugly, not sure why or what the workaround will be. Also finding we have to add a commit line to several of these related scripts to make the last record commit in the master db.

That said, we're glad we did it. The performance gains are great, especially for our remote clients.

Ah the joys of new toys.

[Fenton]

What you're probably seeing is what FileMaker added during the conversion process. It tries very hard to add what is needed to ensure that your existing version 6 scripts work. However, the result is not always exactly what you want. One thing it does, when you Go to Related Records, is to add a Select Window ["file name"], in the related file. This would have been automatic in 6 (though often hidden in scripts that did this, then returned). Unfortunately it also causes the window to flash to the front.

You could remove inappropriate ones. But it sounds like you haven't read much of the documentation about it. It's hard to say exactly which to remove. But, if a Go To Related Record is being used to display the table, it only has to end up on the right layout (critical), it doesn't have to select the window.