Chapter 8
|
Distributing runtime database solutions 83
1 Test your runtime database solution with actual data. This is
especially important if users are upgrading from earlier versions of the
runtime application and need to import data into new solution files.
1 Make sure all the auxiliary files and DLLs (Windows) are present.
1 Show your database solution to intended users to uncover any
usability issues.
1 Install your bundled database files on a completely different
computer to verify that all the files associated with the primary file
can be found.
1 If you’re assigning passwords or permanently removing full access
privileges, test all access levels. Make sure your database solution
contains an About layout that notifies users of the level of access
you’re providing. See
“Creating an About layout” on page 79 and
“Your responsibilities as a developer” on page 82.
Important You should keep an unbound version of any runtime
database solution files, especially if you’ve permanently removed full
access privileges. See
“Removing full access privileges
from databases” on page 73.
Distributing updates to
runtime database solutions
If you make feature enhancements or modifications to the primary
bound file of your runtime database solution, you can distribute the
updated file to your users without rebinding it. If you change the
filename of the primary file, however, you’ll need to rebind the file
and distribute a new version of the runtime application along with the
updated file.
To distribute new or updated auxiliary files for your runtime database
solution, you need to bind them first using the original binding key. If
you are distributing a new auxiliary file that requires new file
references in the main file or that requires other files to interact with
it, you must update all files that have been modified.
If you forget the original binding key for your runtime database
solution and want to update or add a file, you’ll need to rebind all of
the database files with a new binding key and redistribute the entire
solution.
To distribute an updated primary file:
1. Open the original primary file from your copy of the runtime
solution in FileMaker Pro Advanced.
2. Make the changes to the primary file.
3. If necessary, create an Import script so users can import their
existing data into the new primary file.
See “Importing data into upgraded runtime solutions” on page 72.
4. Send your users a copy of the new primary file with instructions to
replace the old primary file in the runtime database solution folder.
To distribute a new or updated auxiliary file:
1. In FileMaker Pro Advanced, create the new auxiliary file or open
the original auxiliary file (before it was bound) and make changes as
required.
2. If necessary, create an Import script so users can import their
existing data into the new file.
See “Importing data into upgraded runtime solutions” on page 72.
3. Use the Developer Utilities to rebind all of the files in the runtime
database solution and include the new or updated auxiliary file.
Use the same binding key that you used for the primary file.
Remember that the binding key is case-sensitive. See
“Binding
databases into runtime database solutions” on page 68.
4. Send your users a copy of the new or updated auxiliary file along
with instructions to place it in the runtime database solution folder,
replacing the old file if appropriate.
As long as the binding key has not changed, you don’t need to
redistribute the runtime application or other solution files.
