"This script cannot be found or has been deleted"

This is the message I get when I try to open one of my scripts. All the
other scripts work perfectly, but something seems to have happened to
this one. I'm guessing it can't be saved, so I tried to delete it, but
it refuses to disappear from the script list.

What do I do here? I can live with recreating the script, but I'd prefer
it not be in the list when it doesn't work.

The file is located on a FileMaker Pro Server 8, running on Mac OS X
10.4. I'm running FileMaker Pro 8, same OS.

--
Thomas Hansen : th(at)ambolt.no : http://www.ambolt.no/

Sounds like the file is corrupt. Deleted scripts should not come back to
haunt you.

Since you can otherwise open it, some combination of saving a clone, running
Recover on it, and -- if you have access to FM8 Advanced (Developer) --
compacting and optimizing the file should eventually get rid of it. I'd be
wary of using the file in production until that script went away.

Bill

"Thomas Hansen" <violon (AT) online (DOT) no> wrote

Be aware that a recovered file is only meant to be used as a rescue-vessel.
It is not meant to keep working with it.
Recovering is only recovering of the data, other flaws me be still active
somewhere. I hope you do have a recent clone without errors so you can
import the data into this after the recovery. After this you should chuck
out the recovered file.

Ursus


"Bill Marriott" <wjm (AT) wjm (DOT) org> schreef in bericht
news:Ld-dnfie18BVOODenZ2dnUVZ_sqdnZ2d (AT) comcast (DOT) com...

Ursus,

You're right, but on the other hand the errors tend to exist well before
they show themselves with problems like the undeletable script. So, going
back to yesterday's copy isn't going to ensure you won't encounter trouble
again.

Until/Unless FileMaker offers a "rebuild file" option, working with a file
that had once been recovered at some point is most users' only option.

Starting with a brand new file and using Copy/Paste... that can copy across
corruption, too.

In fact, other than manually rebuilding a file, the only option I can think
of to be reasonably certain corruption is gone is to use FM Robot. I haven't
used it personally but it would seem to be a nice way to rebuild the logical
elements of a file (tables, relationships, value lists, privilege sets,
custom functions). I don't think it does layouts yet. And there is no
mention of Scripts on its overview page (I'm sure they'd mention that if
they supported it). FM Robot requires FM 7/8 "Developer," and it's not cheap
either ($200). http://www.newmillennium.com/fmrobot

It's not a problem if you have very simple tables, etc., to start over. But
with a complicated database system, you're kind of stuck.

As a practical matter, one usually has to be satisfied with the following
steps:

1) Export the data in the file to a format like tabbed text and verify
everything is there.
2) Save a clone of the file, a copy with no records
3) Recover the clone
4) Compact and Optimize the recovered clone if you have FM8 Advanced
5) Examine the compacted/optimized/recovered clone for corruption
6) Repeat 2, 3, 4, 5 as needed until it appears clean
7) Re-import your data

Bill


"ursus.kirk" <secret (AT) nowhere (DOT) com> wrote

As a developer I would strongly suggest working with "clean files"
only.
Save your files every once in a while when you're working on them, if
FM or the computer crashes then go to the last save. You might loose a
couple of hours now but you won't have to explain to the client that
weird things are going to happen and there isn't much you can do about
it.

So do I, but very few files are truly "clean." Going to the last save often
means the corruption is there, but you won't see it (for a while).

"FP" <ab (AT) pottnerconsulting (DOT) ca> wrote

In article <xd-dnXPwQJsVmOPeRVn-tw (AT) comcast (DOT) com>,
"Bill Marriott" <wjm (AT) wjm (DOT) org> wrote:

Thanks for the help. Fortunately, I'm only working with dummy data for
the moment, as I'm building a new database here and have not yet
imported the data from the old one. I'll try making a clone and recover
it, and hopefully things will work.

When I first discovered this error, the backup created by Filemaker
Server had it as well. Is it possible to make Filemaker Server keep more
than one backup of the databases? Or is the solution to automate an
AppleScript to do it on the server machine?

--
Thomas Hansen : th(at)ambolt.no : http://www.ambolt.no/

It's certainly possible with AppleScript but I wouldn't know offhand what
the script to do so would be. Good luck...

Bill

"Thomas Hansen" <violon (AT) online (DOT) no> wrote

Just rename the old backups with applescript according to date. Providing
you don't back up more then once a day this should do it. Otherwise a plugin
might come in handy. When you just do it once a day you can use the trial
file-plugin from troi. But this will quit working after 45 minutes and then
you have to restart filemaker.
But for doing it just once it is quite good.

Ursus

"Bill Marriott" <wjm (AT) wjm (DOT) org> schreef in bericht
news8CdnR9yMupBMOLeRVn-vw (AT) comcast (DOT) com...