[2005] Sometimes publish overwrites database during install

I have a couple apps I've written with Visual Basic 2005 Express that contain SQL databases. I have been experiencing inconsistent behavior during the installation of updates that I would like some clarification on.

If I update an application to a newer version and install it on a client computer, most of the time it seems to recognize it as an update and keeps the database untouched on the client computer.

Sometimes, however, it will install the blank database I have included in the installation and move the client's database to a .pre directory. This is no big deal, I can just move the data back over, but I don't understand why it happens sometimes and not others. I thought maybe it was just if the database in the setup file is newer than the one on the client machine, but it doesn't seem like this is always the case.

And a 3rd scenario. Sometimes the update seems to be viewed as a new install, not an update. It uses the blank database from the setup routine and does not back up or keep any existing database.

I do not change the name of the application or anything between installs other than appropriately incrementing the publish version number.

Please help me understand what is going on. Am I doing something wrong?

Since it appears that nobody has an answer to my problem, can anybody at least verify that they do not have any problems publishing and installing applications with a sql database like I have described?

Greg

Can anybody see this post? I'm amazed that nobody can offer any help. I view these forums regularly and learn something new almost daily from those of you who share your extensive knowledge. Please, even if you don't know the answer, at least tell me I'm stupid or something for asking this question. This is so frustrating when I publish my application. I don't know what else to do.

Greg

The forum page says that you thread has been viewed 20 times. I don't use ClickOnce so I can't say what the issue might be.

Quote:

---

I don't use ClickOnce so I can't say what the issue might be.

---

Thanks for the reply. What do you use then? Or is ClickOnce just something with the express versions?

Greg

ClickOnce is the only deployment option provided with the Express Editions, other than XCOPY of course. ClickOnce is very useful in situations where it is appropriate, but it's limitations make it unsuitable for my work. Paid-for versions of VS support Windows Installer deployment via Setup projects as well as ClickOnce.