Alex,

I just upgraded 4 projects from 6.0b to 6.1.1 last Tuesday and Wednesday morning then got the email about 6.2 Wednesday late morning. That upgrade was just as involved. I think you have to do the 6.1.1 THEN the 6.1.2. Do you have the 6.1.1 zips?

I'd keep the versions separate. I think all you need to do is keep \MM60b, \MM611 and \MM612 folders and rename the folder you're currently working with to \MMortals.
The downsides are 1. keeping everything straight and 2. getting used to 6.1.2 and not having the new cool stuff when working with the 6.0b (like trying to go back to VFP 6 when working in VFP 7.)



>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