Microsoft Access porting rant

I'm converting an Access db to MS SQL Server for work which is an absolute pain in itself.... SSMA you say ? That amazing product breaks down when it encounters anything mildly complex like porting an Access TRANSFORM PIVOT to TSQL. The tool chokes and says "Crosstab query is not supported". No shit.... but since SQL Server 2005 we've had the PIVOT predicate. Would it honestly be too difficult to program a routine/method into the SSMA wizard to handle TRANSFORM to TSQL PIVOT situations ?

The above rant is not even why I posted today. The icing on the cake is a little predicate in Access called an "iif" statement, and no I didn't spell that wrong. Aparently, some dill hole thought it would be a good idea to have the mentioned "iff" statement instead of banging out the traditional IF ElSE that is in every single language since the dawn of computing. Yes, you can do a traditional IF....ELSE in Access but you can also do the "iif". The reason why we have IEEE, RFCs, and other standardizing methods and organizations is so shit like this doesn't happen, but then again Microsoft has always done their own thing...