>>Where is the data path set from for the application? The path is stored in the user's Registry and in the MetaDBC. Does each user need a MetaDBC when they have the information from their Registry? From other threads here, it seems that the path is read from the MetaDBC but it seems to make more since to read from the Registry. This makes installations more efficient because you can customize the user's registry entries without asking them the startup information the first time they enter the program.>
>
>As mentioned in the Developer's Guide section "Overview of Data Access", by default, the application's database path is stored in the Windows Registry...and if you want to have each user's workstation to point to a different database drive letter, this is a good option.
>
>Alternately, you can follow the directions in the guide for storing the information in the application's MetaDBC.dbf. The Framework uses the database location information stored in MetaDBC.dbf for its builders (i.e. the Business Object builder).
>

The data path seems to be stored in both the Registry and the MetaDBC table. Which one actually controls the framework? If you change one will it change the other? I have the lUseDBCMgrMetaData set to TRUE. Does this change how the data paths are read and from which source?

If you want to automatically set the correct paths during the installation, where do you create the path location (in the Registry and/or the MetaDBC table). When you set this can you eliminate the initial form to appear which asks about where the data is located the first time a machine uses the application?

I have read the manual many times over but I am still unclear about these issues. Thank you for all your clarification.