This is an old thread of mine that has never been resolved.
Are there some heavy hitters about who can help me on it.
If you read the whole thread you will see what my problem is.

The problem is because on our site we have to keep our DATA on different servers from our apps. This means I have to use UNC connections a lot.


It just keeps coming back to haunt me:(


>At our site we are always having to make copys of DATA dolders.
>The vast majority of our applications store all the required tables in the data folder along with the DBC.
>
>Because we have to use UNC paths this means that very often the DBC retains the back link to the source DBC.
>
>This is very bad news if you have just made a copy of your live data and want to work on it in a test area. Using UNC paths can mean that your live data gets screwed because you think you are working on the test data.
>
>Is there anyway of embedding some code in the DBC that will always force a DBC to use the tables stored along side it in the same folder.
>
>I have lots of stuff of my own that resolves back link issues but I am looking for a solution that will make this happen automaticaly with out myself having to remember to resolve the back link issues.
>
>Thanks