Developer’s Guide

5-8 Developer’s Guide
2. If necessary, create an Import script so users can import their
existing data into the new file. (See “Importing data into an upgraded
runtime database solution” on page 2-17 for information.)
3. Use the Developer Tool to rebind all of the files in the runtime
database solution and include the new or updated auxiliary file. (See
“Procedure for binding files” on page 4-6 for information.)
Use the same binding key that you used for the primary file.
Remember that the binding key is case-sensitive.
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.