>> The data environment
>>>uses
>>>explicit paths. I suppose I could dynamically
>>>change the
>>>paths in the .dbc file and in the data
>>environment
>>>in
>>>my apps setup procedure.
>>
>I have taken the approach of use the Gendbc tool
>to recreate
>the data structure on the initial setup of the
>program. I then
>give the client the opportunity to import any
>existing data
>into the new structure. This gets around the old
>path that was
>hard coded.


Allen

Good idea but I am just not 100% comfortable with GenDbc.
The problem I see is keeping GenDbc current. 'If' you add
a new field & index it you must update the GenDbc stuff. With
an INI (ok, I'm a dinasaur...) Any text editor will do.
To me it just boils down to one less step to keep track of.

But I do like your approach for initial setup on the customer
PC especially with empty Data.

Thanks
Tom