Another thread about a dbc not being able to find its tables brought this question up for me - having not yet rolled out many apps in varied situations.

If one stores all dbc(s) and tables (and .exe, etc) in a single directory on development drive of e:, will problems develop if app is eventually installed in directory of same name on drive c: ?

What about directory of different name?

And I should ask the same questions about how a dataenviroment would act in a changed drive:directory location.

I've been assuming that references to tables were relative from apps location rather than explicit from drive letter on down.