Moving to multiple files in 8.5 or 9 is a perfectly respectable and common method of migration. You might also consider it a first 'safe perch'-- after appropriate due diligence, move the files, see how it goes, regain your strength, and then, if you see the need, consolidate into fewer files.
How many files will be dictated by the nature of the system and other considerations, such as the security scheme. It's foolish, for instance, to back up the archive files three times a day, but you certainly would want to frequently back up recent activity, if the database, in fact, handles some sort of activity. That's one easy argument for multiple files. Another is to intelligently allocate connected tables in a large system, such as AR, AP, HR, etc. Having said all this, there's no way to know if the simplest migration to multiples is a good choice for your system, without knowing what you know about that system. Rebuilding from scratch is often a better choice. The issue has been discussed and debated endlessly on this and other lists, as well as in various books and white papers. There is rarely one completely correct answer. By 'due diligence', I mean preparing the system for migration, and extensively testing off line. MetaDataMagic, from NMCI, will greatly help that pre-flight, by looking for potential problem areas, as well as for mis-guided file references, which it can repair on the 6 side. John Weinshel Datagrace Vashon Island, WA (206) 463-1634 Member, FileMaker Business Alliance Certified For FileMaker 8 Certified For FileMaker 7 ________________________________________ From: FileMaker Pro Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Peter Payne Sent: Sunday, July 15, 2007 5:59 PM To: [email protected] Subject: Moving from Filemaker 6 to 8.5 Well, I am WAY behind the curve, I know, having stuck with "old reliable" Filemaker 6 for way too long. Now I've got a Products database that seems to be corrupting itself every 2-3 weeks, which takes the form of certain records that go "bad" and cause the database to crash (cause all users to color wheel to death) when someone accesses one of the damaged records. I've repaired it a few times by exporting the data to "Merge" format and importing it, which basically works, but it's a huge job and I clearly need to move up to Filemaker 8.5 instead. My question is, is it absolutely necessary to remake my databases from scratch, building the multiple tables onto one updated database? Has anyone had experience with converting the mutli-file Filemaker system without reworking the databases into one file? I am mentally against the idea of my entire database being in one big corruptable (?) file, and would like to know if converting and using as-is is likely to be an option? Any advice would be appreciated. -- You've got a friend in Japan http://www.jlist.com
