How do I erased a "damaged script"

[Lambert]

Hello

Anyone know how to fix this?

A script in one of my files started to crash the db., now I want to delete it from scriptmaker. But it cant be removed, the script is still there, and Filemaker prompting the script can't be found or has bin deleted???

It's still visible in the scriptlist and can be moved around there, but it can't be deleted!

[fmdevusa]

This happened to custom function and file recover was the only way.

The id was still in the ddr (xml) report but the name was missing causing a ghost entry in the custom function list. It could not be deleted.

[Lambert]

Hi

What do you mean by, "file recover was the only way"?

Do you mean that I cannot fix the existing file. I don't have a copy of the file where this does'nt happen.

Tryed to delete the script in some backupfiles, the same thing happend whit those files!

[Kris M]

If the file is corrupted (sounds like it is) and you dont have a non corrupted backup then the only completely 100% sure way fix things is to completely rebuild the file from scratch. That means no copy paste or import of ANYTHING from the corrupted file... not even using clip manager. To get the data out of the old file export it into a non fm format (xml, txt, xls whatever) and then import it into the rebuilt solution. You can try the various other methods of recovery but complete from scratch rebuild method is the only 100% way to guarantee your new file has zero corruption.

[fmdevusa]

Lambert is correct.

The recover process removed the problem with the inability to delete the custom function. File Recover was able to remove it automatically.

I do not think you can fix it any other way than the recover or as Lambert states - rebuild manually. Depends on history and planned use for the file and how much effort you deem appropriate to solve the issue.

It is unfortunate that the client's script maker components cannot handle an exception such as what you have and self-correct.