>Over the weekend I purchased a copy of the upgrade from FileMaker 4.1 to >5.5. > >I currently have ebase v1.02. I recently dowloaded v1.03 but it said I >needed an upgrade and my files from v1.02 would have to be converted.
ebase version 1.03 is different from version 1.02 in two ways. First, there are some fixes that squash some bugs that users have found. Second, it is set up for FileMaker version 5.x. FileMaker version 4 and version 5 have mutually incompatible file formats. So the new ebase version 1.03 you downloaded insisted that you use FileMaker version 5 to open the files. To use your ebase 1.02 files with your new FileMaker, you'll need to convert the ebase files to FileMaker version 5. This process is built into FileMaker and is pretty easy. In the other direction, you can migrate your data into ebase version 1.03 files and then use FileMaker version 5. The data will be preserved through this transition, but any structural changes you have made to ebase (new fields, modifications to letters, reports, and other layouts, for example, will need to be re-done in version 1.03. >Now I'm seeing things about ebase version 2.0 coming out in October. >should I wait before converting my current files? I'm a tad confused by >all these versions. I think you have three options... First, do nothing. Continue to use ebase version 1.02 with FileMaker 4.x. If ebase is currently doing what you need, there is nothing to drive an upgrade. Any changes you have made to ebase will not be lost. But, you will continue to use a version with known bugs. Second, squash the bugs in version 1.02 and continue to use it. There is a list of the bugs and fixes for them on the ebase help page. The fixes are mainly revisions to field definitions and are pretty easy for anyone familiar with FileMaker. You could then take the next step if you like and convert the files to FileMaker version 5. At that point you essentially have moved all the way to version 1.03. This is definitely the way to go if you have made many changes to your ebase files. Third, migrate the data to your new copy of version 1.03. If you have not modified ebase very much, this move gets past the bugs with little trouble. There is a readme file in the download package which explains the conversion process. Ebase version 2 is vastly different in structure and the way it looks. It will be released in beta in October. The final version is due at the first of the year. I think it's worth the effort to squash the bugs in your current version, using either the second or third option above. -- -- Dave Shaw H4 Consulting tel: 206-954-7526 fax: 206-625-1338 ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
