>Hi everybody,
>
>I'd like to get reassurance on something I'm about to do.
>
>I have one app developed under MM6.0B that I really don't dare to upgrade to 6.1.2 until I'm comfortable with the new version of the framework. It's quite sizable and really don't need ANY headaches right now.
>
>OTOH, there are three other apps (much smaller in scope) that I want to move to 6.1.2 (two of them are in use and for the other I have only created data structures so far).
>
>Since I don't have a lot of time and want to get started asap, I will install MM6.1.2 in c:\mm612 and leave MM6.0B in c:\mmortals and pray that it works (I think it will).
>
>Am I opening myself for trouble down the road by doing this? Any caveats? Is there any other way to have two versions of the framework coexist?
>
>Thanks!
>
>Alex

I've been using the framework since the early days of time, before men wore shoes and learned that cooking meat tasted better than chewing it raw. I have had as many as four different versions of the framework on my harddrive. No problem. I use the naming convention mmortals20, mmortals32, blah, blah. The reason I did this is because I worked in a busy environment that demanded I keep creating new applications, but I didn't find it necessasry to upgrade every single app I wrote. However, I did have to maintain them. Hence, the multiple versions. Why didn't I stick to one version that worked well? The answer is beyond all else, the framework is a tool for learning and implementing new technologies. With each new version, newer and cooler stuff gets utilized. By using each new version, I am constantly growing as a programmer. Generally, each new release is fairly stable. (Although I've seen some *real* bumpy curves now and again!)

The framework has some nice tools for changing directories and upgrading to the latest and greatest. The only caveat is jumping multiple version is not always smooth. If you want to upgrade from 4.2 to 6.2, I recommend going through all the releases to ensure you have everything.

If you have multiple versions of the framework, makes sure you don't start using class libs from different common directories. This will play havac with your mind.

If this doesn't your question, I'd be happy to rig some electrical wires to your nipples and begin electroshock therapy. <g>