Some scripts go freezing by changing the layout and fields 'online' on filemaker server. And then its impossible to work with this damaged scripts and they cannot delete from the scriptmaker register. There must be a bug in filemaker 8. Have anyone an idea? How can I delete a script when filemaker say "this script doesn't exist"?

I've find out! 'File menu >Recover' repaired the damaged file. Well - its not a bug, but a sign that filemaker 8 isn't stable enough. :

Corruption is not unique to v8.

How many times has the file been close improperly?

How many times have you had to use Recover on the file?

Were you working on the file while it was being served?

Are you using the most recent version of 8 (8.0v3)?

BTW, do not continue to use a file that you have had to use Recover on. Recover is meant to fix the file enough so that you can get at your data, and move to a clean back up copy of the file.

HTH

Lee

Edited September 4, 200619 yr by Guest
v8 addition

move to a clean back up copy of the file

Lee, can you elaborate a little on this. Outside of the server environment (a standalone PC with single user), what is considered a "best practice" for recovery? Is importing to a cloned copy best? This has been a area of concern -- and more than a little confusion -- for me.

Outside of the server environment (a standalone PC with single user), what is considered a "best practice" for recovery?

There are some white papers available that can do a better job on this subject the me. Do a search of the Articles Topic, there links for Core Solutions, Foundation Database Systems (aka Code Masters, and don't for get the FileMaker Site. I remember a link to an Article about Corruption so start here

Is importing to a cloned copy best? This has been a area of concern -- and more than a little confusion -- for me.

Plan for the worst, and hope for the best.

HTH

Lee

Now that's more like what I was hoping to find.

Maybe someone can start a permanent topic in Tips and Tricks to help centralize knowledge on this very important subject.

Anyway, thanks, Lee