لطفا منتظر باشید ...
Pre-Conversion Issues
Before converting existing databases into FileMaker 7, you should consider your options.The biggest decision is whether to combine separate databases into the new multitable file format used in FileMaker 7. Since external relationships work in the same way as all relationships did in previous versions of FileMaker, it is not absolutely necessary to change the existing structure. The converted files will have all of their relationships updated automatically. That might lead you, at first, to want to just leave things as they are. But you don't gain the benefit of many of the new format's best qualities if you maintain your old database structure when you convert. Version 7 is very different from its predecessors, and is, frankly, much easier to manage and distribute over a network.If you do consider converting external files into tables within a single database, keep in mind that when you convert from earlier versions, only one table can be created at a time. You will have to recreate the structures of the other files manually (as tables in the database) and then import the data. That turns a simple series of automated file conversions into a major project, and you may just not have enough time before you have to roll out the new versions.
TipBefore converting to FileMaker 7, make backup copies of the original files. You should make an extra copy of all of the files on a separate drive (or burn them to a CD).Convert or Rework?
How do you know when to take the time to rework your database, and when it's not worth the trouble? Of course, every situation is unique, but in general, consider these issues.Retain Existing Structures for:Simple systems that work in earlier versions.If your current system works well and requires none of the new features of FileMaker 7, you can use it as is.
Complex, multifile systems.If the current system is in constant use and converting external databases will require much development and downtime, retaining the existing structure might be the best approach.
Databases with scripts that call external scripts.If the existing system has many separate databases and uses scripts to move from file to file, converting the databases to tables will also require extensive updates to the navigation scripts.
Multifile solutions with files that are under ongoing development.Systems that are in ongoing development, requiring frequent replacement of databases with updated versions, will take more time to implement, since every replacement will entail importing the data from each file in the existing database into a separate table in the updated version.
Make a New Structure for:Relatively simple systems that have many separate files.If you have built a straightforward database by creating separate lookup files to hold limited types of information (like a database file made up only of a title and description that links into the main file), you'll have fewer open files on the server, and fewer errors.
Systems that require the new features of FileMaker 7.If you want to extend the capabilities of an existing system to take advantage of features like the stronger security model or conditional relationships, you can take the opportunity to streamline the system and fold smaller databases into tables.
Solutions that are in an early stage of development.If the current system is in its infancy and not in constant use, it can easily be adapted to FileMaker 7 without interrupting workflow.
