So you don't think it is a bug for the setup.asp code to use strTablePrefix sometimes and strMemberTablePrefix others? For example:
Lines#3634-3637:
SpecialSQL12(Access) = "ALTER TABLE " & strTablePrefix & "MEMBERS ALTER COLUMN M_IP TEXT (50) "
SpecialSQL12(SQL6) = "ALTER TABLE " & strTablePrefix & "MEMBERS ALTER COLUMN M_IP VARCHAR (50) '000.000.000.000' "
SpecialSQL12(SQL7) = "ALTER TABLE " & strTablePrefix & "MEMBERS ALTER COLUMN M_IP NVARCHAR (50) '000.000.000.000' "
SpecialSQL12(MySql) = "ALTER TABLE " & strTablePrefix & "MEMBERS MODIFY M_IP VARCHAR (50) DEFAULT '000.000.000.000' "
Lines#3736-3739:
SpecialSQL12(Access) = "ALTER TABLE " & strMemberTablePrefix & "MEMBERS ADD M_ALLOWEMAIL smallint DEFAULT 0 "
SpecialSQL12(SQL6) = "ALTER TABLE " & strMemberTablePrefix & "MEMBERS ADD M_ALLOWEMAIL smallint DEFAULT 0 "
SpecialSQL12(SQL7) = "ALTER TABLE " & strMemberTablePrefix & "MEMBERS ADD M_ALLOWEMAIL smallint DEFAULT 0 "
SpecialSQL12(MySql) = "ALTER TABLE " & strMemberTablePrefix & "MEMBERS ADD M_ALLOWEMAIL smallint DEFAULT 0"
If the prefixes are different, doesn't it look like this will generate errors during upgrade of previous version forums?