Scriptmaker

[fmsavey]

I inadvertently opened a file that I was working on in FM 8.5 Advanced with FM 9. When I opened scriptmaker is when I realized I was in FM 9. I immediated closed out of FM 9 and opened FM 8.5 Advanced and the solution. I entered scriptmaker and created a new script. After adding a few script steps I exited the script and then attemped to move the script up the list. When I released the mouse button I did not see the script in the new position. What I did notice was a duplicate of the script that was above where I thought I placed it. When I dragged the "duplicate" script down to the end of the list it changed back to the script I just created. When I move a script (any script) to a new position it takes the name of the script above it. When I open that script it opens the script with that name. I did a recover and still have the same problem. I cannot help but think that this happened because I opened the file in FM 9. Anyone have this problem and is there a remedy?

[LaRetta]

Well, here is the specific Tech Info article about it.

It sounds like you are doing it right but you might have to correct it within vs. 9 instead of 8.5.

[fmsavey]

Thank you, thank you, thank you! I love this forum.

[Fitch]

Thanks, LaRetta, I hadn't seen that one. Wow. Here is FileMaker Inc. specifically recommending that we Recover and then continue to use the file, while the FMI engineers continue to warn against this practice.

[LaRetta]

Oh, Tom, that is too funny. Because the reason I happened to have this Tech Info hanging around was precisely because I as irate that it recommended Recover and for exactly the reason you indicated; the dichotomy of it! And I actually ranted on another thread about it. Ha ha! Worse still is that I then pass it on to someone as an answer to their problem. Lord help me ...

Well thank you for mentioning it that Recover isn't recommended. Uhm, fmsavy, I don't recommend using a file which has been recovered. Uhhm, err, use a good method of determining what to do here ... a dart board.

[comment]

I am only speculating, but I think the warning applies to recovering CRASHED or CORRUPTED files - where some parts need to be reconstructed by guessing.

[Colin Keefe]

I remember this from your previous rant, LaRetta - it's my favorite Tech Info article, not only for its unrecommended "recommendation", but its description of the problem:

"This weird behavior makes it virtually unworkable"

Gotta love that. It's almost like they copied the description verbatim from a hate email.

[LaRetta]

Hmmm, well crashed or corrupted files wouldn't need this:

You will need to manually move each script to the appropriate position.

... which truly sounds like leaving the scripts in the recovered file, repositioning them and ... continuing to use it. Otherwise, why would someone need to move them to the 'appropriate' position? That's MY take on it anyway but I'm frequently wrong (truly). :crazy2:

[comment]

Yes, continuing to use the recovered file - if the recovery wasn't due to major corruption.

Again, just a speculation.

[LaRetta]

I think I see what you are saying, Michael. And, although FileMaker says vs. 9 is much better at recovery, I do not believe one can be sure a file - ANY FILE - hasn't experienced some sort of questionable portions. And prior versions of FileMaker would wipe out any questioinable spots even in a good file. It is similar to the scandisk days with DOS - a cluster was marked bad and never used again even if it is very slightly questionable. And that stance is fine if that questionable spot doesn't contain your FileMaker design but it does. And we aren't even told WHERE the recovery took place. Worthless.

My stance has always been that, once a file has been Recovered, it should never be used again. As we move forward in versions, we may be able to trust the recovery process a bit more but, as of today, I still do not. The recovery message can easily say 0 recovered all the way through but it has been inaccurate. I have files that produced this 'clean' message that have damage from crash (custom functions take nosedive usually first).

So I still disagree with the suggestion. And no, I have no alternatives. But if I could get my hands on a file with this condition, I would love to try to find a solution other than running Recover.

[Colin Keefe]

FWIW, we just experienced a variation of this.

Two developers logging onto a remote client to perform work; one had to open up 8.5 Advanced, because the other had 9 open - they were the client's box copy licenses.

Three scripts created in 8.5 are not visible in ScriptMaker when the ScriptMaker window is viewed in 9. Script still works, attached to button, etc, but it just ain't there to be moved around in 9.

Renaming or moving the script in 8.5 doesn't seem to do a thing. There are lots of Script Groups in this file, which I'm guessing has something to do with what's going on.

Anyway, we're just going to replicate the scripts in 9 on a backup, delete the old in 8, and see what transpires. If that works, we'll take it back into production.

It is interesting, though. Usually when FileMaker breaks, it's on something I can perceive as being a tough problem - like managing printing options on multiple platforms. It's not often something in the developer environment itself is this wonky.