Well guess i will dredge up an old thread.

I was using the publish feature on a windows app and I thought I had my settings right to not overwrite the database however I must of been wrong.

Because a user took my update and lost all there data arghh. So what is best way to handle this? I dont want to make any other users frustrated

I thought if I had the "copy to output directory= do not copy" i wold of avoided this.

So how do i avoid this? Maybe i changed the publish location..dunno

thanks
Quote Originally Posted by ghall426
Using click once, I don't have anything like that screen. From Visual Basic Help, this is what happens to SQL files:



Maybe I'm being dumb, but what do they mean by migrate? Is this more of a merge than an overwrite? It seems like it is doing a complete overwrite to me, leaving me with whatever data is in the database of the update.