Problems going from Access 2003 to 2010
Posted on 2012-03-16
I installed Office 2010 including Access over Ofice 2003, and I get a number of problems with some apps which worked flawlessly under 2003:
- first problem was with PtrSafe, that was easy to fix
- second problem was with an MS progress meter (of class MSComctlLib.ProgCtrl.2), which did not work any more because the .Value attribute was not a valid attribute at run time. What's the natural replacement in 2010 for an "old" progress meter ? Or is there a way to have the old one working ?
- When I tried to repalce that progress meter with an ActiveX ProgView class (hoping it was a progress meter...), Access told me the OLE server was missing and I should reinstall it. How do I do that ?
- When running code which saves form fields to a SQLServer DB, some text box fields returned padded with a lot of trailing spaces, so that they are too long for the corresponding DB field (same symptom as when one declares a field in the DB as char(x) instead of varchar(x)and fetches the DB field content, only here it's the other way around: a new, empty field is populated based on a fixed value list with items of, say, length 1, but the reurned field contant has a length of 8 or 10 characters because of the trailing spaces). Which text box attribute is causing that, and why are only certain text boxes affected and not all ?
Thanks for your help.