I ran into a problem that puzzles me (and haunts me).

I just upgraded a file to be run on FM server 8 and it no longer opens to the "Normal" status. I have checked the usual suspects (fmapp checkbox, multiuser status etc, ran file maintenance programs) but everything seems OK. Also 3 other files on that server open OK.

The file opens w/o any problem or error report locally using FM8.5 Advanced, also on the PC where the server runs, using a local FM-Pro 8, but when I try to start up all files with FM-Server, the Normal status flashes up for a millisecond for the problem file, then closes again.

The upgrade did involve some minor scripting but as far as I know nothing that would introduce this sort of behaviour (although you never know of course).

So my question is basicly this, what can trigger FM Server to shut the a file opening process?

The log file did not give much clues but I did not have a lot of time to read through it line by line as the office closed.

Any help would be highly appreciated.

Peter

FMS8 does a consistency check and your file probably failed that. Check the event log to make sure that's the problem.

If it is, open the file locally and do a "save copy compressed" and the file will likely pass the check on FMS.

More important though, you may need to check some backups of that file to find one that does pass the check and import your data into that one. Not passing the consistency check may be a sign of trouble in the file.

Thank you Wim, that was a helpful suggestion. I will check the logfile when the office opens again on Monday and do some debugging meanwhile. Fortunately I have plenty of intermediate backup copies to track down the changes that was the causing this. I will post the findings if I can really trace it fully and when it seems useful for others.