>
>Hi Jerry,
>
>Now there's an offer that's difficult to refuse :-)

Good, then when ever you are passing through Lincoln you'll find the State Office Bldg at 301 Centeniall Mall South, and I am on the second floor, the Revenue division.

>
>Your message got me thinking and I went back to the online docs to see what MS recommends to do about managing DB's. They say not only to not Sourcesafe control the DB but also, to ensure that each developer does not maintain their own local copy of the DB.

Are they saying to put the DBC (+ tables?) in the project directory of the server vss?

> Otherwise it becomes a very tricky task to try and merge the changes made to the DB at a later point (That I have learned from experience). My problem was that to share the DB it would be necessary to put the DBC on a different drive than my source code. As soon as the DBC is on a different drive than the source, all references to the DBC that are stored in forms' dataenvironments become absolute instead of relative. This leaves me with one decision, do I want an absolute path that contains a drive letter and make sure all developers have the same drive mapping to access the data, or do I use UNC to guarantee that everyone is pointing to the same data. The problem with UNC is it permanently fixes the design time location of your data.
>Anyway, I am working with a UNC absolute path to my data at the moment, I'll let you know if I find out I've made the wrong decision.
>
>Darrel

I have been thinking aboutr that problem also, along with the decision of where to put the exe. The data has to be on the network, but the install program puts the program +dlls on the local harddrive. I've been thinking of deleting the local app.exe after installation and having one exe on the network along with the data tables.

Jerry