Leaving Records Open?

[Jalz]

Hi Guys,

I've almost finished migrating one of my FMP 5 solutions to an FMP 8 format. I've even imported a couple of tables togther to see how the import table feature works, and now I have a solution with 18 files instead of 22.

One of the things I've noticed with regards to External FP7 Files, it takes a while, almost 2-3 minutes to open up the related files. Comparing this to FMP 5 which opens the original set of files in 30 seconds. FMP8 seems to open up the files quicker if I'm a guest(i.e. network) environment than standalone...but then again it could be the way I've configured the files. Probably go ro FMP Knowledgebase and see if there are any articles on this.

Anyway I have one problem that needs to be solved sooner rather than later. I've got an opening script which opens all the files and set a couple of fields to hold a value. Now each setfield script has a commit script step underneath. Onece the routine has opened and initialised my files When I try to run a script in the in the main file, it gives me the error message that the record is being modified elsewhere (can't remember the message exactly until Im back in the office). Im assuming the the record is open for editing but does anyone know what else could leave the record open apart from the Setfield command?

Cheers.

Jalz

[Ted S]

Jalz,

If you haven't already done so take a look at the File References section in your converted solution. You may be surprised at what you find in there. After I converted mine it was a real walk down memory lane because it contained a reference to every file and computer that was ever related. These unnecessary references can really slow a system down. Delete any that are not current.

[Jalz]

Hi Ted S,

Yes, I've cleaned all of those up....boy those were quite messy after the conversion. The only other major issue I encountered was the correct windows not displaying, but that was easy to sort out with the new Select Window command.

[Jalz]

Hi Guys,

Just to let you know, went through all my scripts and added a commit script after each block of Setfields, Sorts and anything I thought could leave the record open. Its now solved. It would be useful if we had matrix that lists commands that could leave records open....

I've also solved my issue with speed. It was to do with file references. The references themselves were clean, i.e. say I had two files, preferences.fp7 and customer.fp7.

In my pereferences file I had the following references

fmnet:/*/customer.fp7

file:customer.fp7

Well I thought for a network installations, I needed the fmnet reference - p.s. the reason Im using an "*" is because I do many installations for my product and each host machine has a different IP address. I was wrong in using fmnet as the only file reference i need is file:customer.fp7 as this works across a network anyway. So if file:filename.fp7 works, in what circustnaces do we use fmnet?

FMP 8 is good fun

[Steven H. Blackwell]

You--and others converting from FMP 6 and earlier-- may want to run MetadataMagic and FileRefrence Fixer on the files **before** you convert them to clean up errant file references. The idea is to consoldiate the duplicate references before conversion.

Steven