ScriptMaker reorder problem

[macpaperpusher]

My solution, started many years ago through 4, 7, 8 and 8.5, works perfectly. I'm starting a renewed effort to rework the database except that ScriptMaker scripts now refuse to reorder and when the script is dragged and dropped to it's new position, the script assumes the name of a script below the dropped script. I can actually have several scripts with the same name. If I click on one of those scripts to open it, it shows the correct script contents for the title but after closing that script, the script below it now assumes the name of the script below it.... and on and on.

When I OK ScriptMaker to close and then reopen, the scripts are in their original order...... in other words, I am unable to reorder any scripts. There are about 35 scripts.

I have gone backwards to backups of over a year ago and the problem still exists. It doesn't occur with a new database but that is based on limited testing and data. I assume my Scriptmaker is hosed.

I was about to cut and paste each script out and then back in on a test backup but...... any other ideas.

Thanks

John.....

[Ender]

I have not seen or heard of this problem. Have you been able to reproduce this on different machines? In which specific versions of FMP does this happen?

[macpaperpusher]

3 machines (2 - G4 Cubes (OSX 3.9 and 4.8) & 1 - G4 Powerbook (OSX 4.8). The problem has been reproduced on all 3 machines in all combinations...... either serving or not.

Specifically, have tried the solution on FMP 7.03, FMP 8.03 FMP 8.03 Advanced and 8.5 Advanced... all with the same results.

Problem has survived shutdowns, duplication and all of the above so that would seem to confirm that my solution is at fault.

Thanks

John....

[Ender]

Unfortunately, that only points the file as being the problem. And even though it's a minor problem with the script name, it's a sign of file corruption. With the corruption being present in your archives for the last year, it's going to be a pain to resolve.

My recommendation is to rebuild the file from scratch. If you only have 35 scripts, then the file probably isn't that complex, so this shouldn't be a huge undertaking. If you plan on reusing those problem scripts, make a backup of the new working file before importing the scripts in from the bad file, just in case the corruption is carried in the underlying script code.

[macpaperpusher]

Apparently solved by deleting all scripts and then cut/paste scripts from last backup.

Thanks

John....

[Lee Smith]

If you have a clean backup, why not just use a copy of it, and then inport your current data into it?

IMO, ScriptMaker has just told you that your file is corrupt. To continue to use it is exposing your data to data loss.

Lee

Edited January 17, 2007 by Guest