20 May 08 19:10
Sounds like you had a SQL server upgrade in there too.
Access 2003 does not support SQL 2005 for design changes. It has something to do with the extended properties, I think. The only way to manage SQL 2005 objects if your using Access 2003 is to not use Access. I bet Access 2007 was getting confused by extended properties and cleaned them up with what you did.
I have a hunch that making a copy of the front end and upgrading to 2007 ADP would have fixed the problem. I still use Access 2003 so don't look for a test from me in the near future.
I aggree though it is a stupid bug. So is depricating the functionality to use Access import specifications programmatically in 2007.
Honestly, having gone through an MDB to ADP migration, I don't see the point. I would much rather keep all the MDB functionallity and deal with pass thru queries and code to manage updates instead.
It seems to me that Access 97 was the version that did what it was supposed to. Although, ADO is good if you are not working with JET data. But who needs a UNIFIED help system and the ability to build to controls in code anyways?
Sorry about the Soapbox... you got me started with the comment about current Microsoft technology stinking.
I'm definitely deprecating my upgrade budget for Office.
Funny thing, I thought office sales generated more revenue than Visual Studio .NET and OpenOffice.