Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 8336 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

in 5.0v1 is it common for files to get corrupted? I have had this a couple of times. The Recover ... function says its worked but as soon as the file is opened FM quits and needs a restart as it claims I still have a copy running after it's quit!

ps. I hope this is an appropriate place for this message - I couldn't see a better one.

Posted

quote:

Originally posted by RH:

in 5.0v1 is it common for files to get corrupted? I have had this a couple of times. The Recover ... function says its worked but as soon as the file is opened FM quits and needs a restart as it claims I still have a copy running after it's quit!

ps. I hope this is an appropriate place for this message - I couldn't see a better one.

First, get the 5.0v3 updater off the FMI site. It has many fixes.

Second, don't use Recovered files. The purpose of Recover is to extract the data for insertion into a clean clone.

The message you're getting most likely indicates that you have a duplicate copy of FileMaker Pro running on the network. Each copy must have its own serial number.

HTH

Old Advance Man

  • Newbies
Posted

OK thanks - the message is part of the crash eg. it's not properly quitting - cos I only have one copy installed and I'm not networked!

I take th epoint on the 'recover' function.

What is the FMI site please? The official filemaker site at filemaker.co.uk has dead links to updaters (I did look cos I thought an update might fix the problem ...)

This topic is 8336 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.