Hi Mike,

I had thought of doing this with a batch file in the user's startup group using just xcopy with the "skip if same" switch on so that it is up to date even before the user goes to use it. Probably using a launcher though would give me more control.

On this subject, I have not addressed the problem of having my dbc views up on the network - every now and then users get the dreaded 2005 error that kicks them out of the app because someone else is firing up the identical view at the same time and the 2nd guy in cannot fetch the view from the dbc. I thought that VMP was going to introduce some framework changes to handle opening views differently to address this problem (but don't know if they did or not). Unfortunately, this client is currently stuck at VMP 4 (believe it or not). I was dutifully applying all changes/patches up to that point and then they stopped development of the app for over a year. When I got back to it, they were chomping at the bit to do some "priority" tasks and I never was able to take the time to move their code up to the latest version. I have mentioned that I need to do this for them this year as a priority job.

So I don't know if moving their app to VMP-whatever-it-is will open up the ability to get around the error 2005 or whether I need to instead develop the launcher and copy the dbc down to their desktop. The dbc does not use dbc generated keys (it uses an older key table) and so I don't think there is any reason I cannot copy it down to the network.....only issue is will they let me take the time to implement the change (they ususally do).

Anyhow, any suggestions re VMP upgrading or whatever are appreciated.

Thanks.

Albert