2 is your best practice. 1 is likely to work for you, but there are no guarantees--hence 2 being the better practice.
Yesterday, I was using FileMaker Pro 11 Advanced on Mac OS X 10.6.8 to remote open and edit a client's database over the Internet.
I don't recommend doing that to modify the design of a database. Connection glitches can damage your file if they take place while design changes are being committed back to the file and the damage may not be noticeable for quite some time.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.