Several years ago built a database for a customer using FileMaker 7. The
customer is now using FileMaker 9 on Windows, I am using FIleMaker 11
Advanced on Mac.

The production database works as expected. However, we recently
discovered that copies made using File>>Save As have an error in the
script catalog. Discovered this because some scripts marked to show up
in the script menu do not show up in the copies. The same scripts do
show up in the production database, but not in the copies. Discovered
this is true of copies going back to 2008, including clones I made.

Ran File>>Recover using FMP 11 Adv. This finds and error and warns that
the database is not safe to use going forward.

Made a compacted copy, deleted all the script, made a compacted copy of
that, and ran Recover on that file, which shows no scripts in the Manage
Scripts window. Got the same error report in the Recover log.

The relevant part of the Recover log reads as follows:

2011-01-30 17:02:58.800 -0500 SVDPTracker DevC.fp7 0 Recovering: script
catalog
2011-01-30 17:02:58.800 -0500 SVDPTracker DevC.fp7 0 Rebuilding
script catalog order list: quick reference
2011-01-30 17:02:58.801 -0500 SVDPTracker DevC.fp7 0 Rebuilding
script catalog order list: name
2011-01-30 17:02:58.802 -0500 SVDPTracker DevC.fp7 0 Rebuilding
script catalog order list: custom
2011-01-30 17:02:58.802 -0500 SVDPTracker DevC.fp7 0 Recovering:
script '--' (354)
2011-01-30 17:02:58.803 -0500 SVDPTracker DevC.fp7 8496 Balanced out
begin and end folder markers



Apparently Recover is finding a script named "--" that does not show up
in the Manage Scripts window.

The recover log shows the same error no matter what I do to the file
before I run Recover.

Any idea what might have caused this?

Do I ned to rebuild the database from scratch to recover from this, or
is there some less drastic action that could fix it?

The database has 26 tables, 64 relationships, 116 layouts, 43 value
lists, 156 scripts, so rebuild is not a trivial undertaking.

--
Bill Collins

On 31/01/11 9:34 AM, Bill wrote:

I could be wrong on this, but as I recall from versions around this
time, (7,9) even FileMaker position was Save as copy was not a reliable,
nor recommended process.

I do recall discussions from others suggesting the same thing.

Bill <bbcollins (AT) earthlink (DOT) net> wrote:

Sure thing. Still, with Filemaker Advanced, the main work is to rebuild
the relation graph. A hard copy of a DDR will help you there. You can
copy the tables first, and layouts and scripts afterwards.
--
http://clk.ch

On 31/01/11 5:43 PM, Christoph Kaufmann wrote:

Some would council against copying anything. A virgin rebuild from
scratch is the only way to guarantee no propagating corruption. THe RG
is the easy part; 64 rels is nothing :-)