Fixing the "MS Access automated reference updating" is huge. My solution is that I still develop my base application in MS Access 2003. Because my clients still have MS Access 2003. (Side note: the MS Access Run-Time for Access 2013 is the first decent representation of the Design Environment MS Access.) I (feel that I) know first hand that developing with a later version of MS Access is better for me, but then I cannot regress the product to run on the client's computer(s).
= = =
Conversely, it takes strong discipline to NOT USE capabilities in later versions of MS Access when the base deliverable is to be compatible with MS Access 2003.
--- Conclusion: Visual Studio has detection of compliance of solution with prior versions of dotNET environments. MS Access should have similar capability.
Fixing the "MS Access automated reference updating" is huge. My solution is that I still develop my base application in MS Access 2003. Because my clients still have MS Access 2003. (Side note: the MS Access Run-Time for Access 2013 is the first decent representation of the Design Environment MS Access.) I (feel that I) know first hand that developing with a later version of MS Access is better for me, but then I cannot regress the product to run on the client's computer(s).
= = =
Conversely, it takes strong discipline to NOT USE capabilities in later versions of MS Access when the base deliverable is to be compatible with MS Access 2003.
--- Conclusion: Visual Studio has detection of compliance of solution with prior versions of dotNET environments. MS Access should have similar capability.