Not sure if this is correct or not, but I think when a MP3 is installed, what is done is first copying or renaming ALL old tables into new tables. From Mpa2 to Mpa3
To speed up that process, you first do the rename / copy part, verify data is handled correct and THEN you "drop unused" fields.
Setup process is usually done through scripts, like the SQL script (did not see the code, was 404), since they had a lot of old customers wanted to upgrade, and most likely a lot of new customers because of the version update, then I could suspect they delay the "boring part", wich is writing new install scripts.
As they would already have a install script for Mpa2, and they already have the database converter script it is most likely a lot faster setting up the DB for Mpa2 and then do the upgrade to Mpa3.
Then you dont need "2 sets of install scripts", 2 sets of install scripts is also bad, especially after a version update since you need to change same data 2 places, giving higher riscs for errors whenever a bug is detected.
I do have a server with a Mpa3 copy installed, no longer active, as a programmer I ofcourse spend a lot of time going through all the files (many are encoded though) and also spend alot of time going through the database structure, and there was absolutely nothing showing evidence of any kind of shaving mechanism build into mpa3.
Oystein your office is a long way away from Denmark, can you just E-mail me the full source instead??
