Our office runs Filemaker Server 9 to which appox. 10 Filemaker Pro 9 clients connect. I spend that last few months developing the database on my computer using Filemaker Pro Advanced 9. After testing, I moved the database to the server about two weeks ago and it has been in use since.

To create a new record, the user runs a script that opens a window above the list of all records. Once they enter all the data, they run another script that validates the information, set up some relationship, and then closes the data input window.

Today, a user followed this procedure to create a new record. However, when she viewed the new record, all of the data that she entered had been replaced by data from a record that had been deleted (in fact, this record only existed when I was developing the database on my computer and was deleted before I ever moved the database to the server).

Can anyone provide an explaination and/or solution to ensure that this does not happen again. Could this mean that my database is either corrupted or on the road to being corrupted?

It may be a problem with the scripting, especially since it sounds like it'd doing some fancy things.

But to be safe, close the file on the server and save a compressed copy, and host the new copy.

Also get your backups in order in case anything goes wrong.

Are you using global fields for any of your purposes here cos they start up in server with the last values when hosted as a single user - just stabbin' in the dark though

Phil

Phil:

Great call on the global field. The explains where the 'old' data came from. The user assured me that she had initially seen the correct data, but must have been moving too fast and not realized that the incorrect data was present.

Vaughan:

You mentioned closing the database on the server and then 'saving a compressed copy'. Seems like that may not be necessary based on Phil's observation, but I would like to add it to my bag of tricks for any future problems. Can you elaborate on what you mean by 'save compressed copy.'

Many thanks to both of you for your quick responses.

Edited October 3, 200817 yr by Guest

1. Disconnect users.

2. Close all files.

3. Stop the FileMaker Server service/daemon.

4. Open file in FileMaker Pro and from the file menu select save a copy as compacted.

This can repair some types of file damage.

[color:red]Do not use the file "maintenance" tools of compact or optimize found in the Tools menu. They will further damage an already damaged file. I am doing my utmost to get FMI to kill these.

Steven