filemaker pro database graph copy graphic

If you are investigating a problem and you can determine roughly the date that the issue first appeared, you may want to prepare two clones-one representing the current state and another clone of a back-up that you believe predates the issue. Instead, you must first obtain a backup copy from your server administrator before proceeding with the steps below.

Note: If your database is currently hosted, you will not be able to make a clone of it directly. Before sending the clone to your technical support person, you will need to make sure that you have added an account for this person to the file if he/she does not already have authorization to view the file-clones include all security settings of the original file even though the table data has been stripped out. A clone is a copy of the database with no records in it.

If you have access to the physical server or location of a stand-alone file, you can send a clone of a back-up or, if working with a stand-alone file, a clone of the actual file. Sending a full copy of a database to the Help Desk is not recommended both for size and data security reasons. This may also necessitate sending a copy of the database. When troubleshooting databases for functional issues (as opposed to data entry issues), it's often necessary for the person doing the troubleshooting to examine the structure of the database using a copy of the database. How do I send the Help Desk a clone of my FileMaker database? How to create a clone of a FileMaker database

Filemaker pro database graph copy graphic