>Hi Naomi, thanks for answering.
>
>Are these projects totally separate? Is it a branch? If you make a change to the currently production project, how do you make sure that the change also goes to the development project?
>
>So I'm guessing you never have to go a version that is 2 versions back, let's say the last version at the client is 3, but another client has version 2 and you need to make a change to version 2, do you run into this situation? How do you handle it?
>
>Thanks.

They are totally separate. We use Source of Site (which is Web Based VSS as Craig B explained to me). Some of the code is shared between different projects. Still the previous project (and its shared libraries) are separate from the current project (and its libraries).

So, we have, MainApp4058 - this is current production
and MainApp - currently in development.

We're making changes in MainApp mostly, but if we need to fix a problem in the production version, we grab forms/classes, etc. from MainApp4058 and make changes there.

Sometimes we need to make the same change in both versions. In this case we update both forms (or classes or programs) separately.

All developers are not happy with this arrangment, but at least we don't mix versions too much.

We're trying to keep clients on the same version. If a client has a previous version and encounteres a bug, we verify if it's still in the current production version and then upgrade that client to the most recent production version.

Sometimes we also may need to change the database. Usually we provide database upgrade scripts, but in certain cases my colleague provides custom scripts to fix a particular problem.