My initial problem was that the database file included in my application installation would overwrite the database file on a client's computer whenever they would run an update of my program off CD.

My workaround was to only include a blank database with the installation. When the app is started, it will search for the real database and if it doesn't exist, it copies over the blank database.

But now I notice that an install does not necessarily go in the same folder as a previous installation. Some times it does, some times it doesn't. I'm not real sure as to how or why this happens. It's in the "Documents and Settings/user/local settings/apps/2.0/" then 2 or 3 folders of random numbers and letters.

Does anybody explain the above procedure or have a better workaround for the problem I'm having?

Greg