on 11/10/00 12:41 PM, Larry B at [EMAIL PROTECTED] wrote: Larry, My advice is to not change the extensions, with a caveat (see below). > 1. If anyone can explain reasons I should NOT change the file extensions, > could you share them? The file extensions are encoded into all relationships between files. If you change them, you will have to reset all of the relationships in the database. This will be very time consuming and fraught with possible mistakes. > > 2. Could someone with expertise please verify whether I properly understood > the reasons for use of the "102" extensions, or offer some clarification? Well the reason is so that you could tell which version of ebase you were running. There were several versions, and it was much easier to do an upgrade between versions is you could run both copies of ebase on the same machine. The only way to do that is to have different extensions on different versions. If you are serious about changing the file extensions, I would recommend getting FileMaker Developer. It includes the application used to create the runtime version of FileMaker. It includes a feature to rename the file extensions. It automatically does all of the relationship changing. Marshall ---------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------- Marshall Mayer mailto:[EMAIL PROTECTED] Principal, TechRocks http://www.techrocks.org 38 South Last Chance Gulch - Suite 2A Helena, MT 59601 eFax: 208.361.0149 ---------------------------------------------------------------------- Please note my new email ([EMAIL PROTECTED]) and street address. ----------------------------------------------------------------------
