Problems going from Access 2003 to 2010
Hi
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.
Bernard
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.
Bernard
ASKER
Hi
Thanks for answers. I know I asked 3 questions in one post, and there is a reason to that: I am currently on a short holiday in Sweden in a place where there is no land line and virtually no GSM reception, so the Internet down/upload speeds to my USB modem-equipped laptop are measured in double-digits kbps, typically in the 20 to 30 kbps (!), so every post takes ages and is a real torture with the current fancy web sites like the EE site. That's why I packed all in one post.
Yes, it's a 64 bit machine adn Office 2010 64-bit.
What are the "native methods" of showing a progress bar ? Can you be more specific ?
I found the problem on the text and combo boxes. It was my fault. Some of the fields in the DB were wrongly defined with fixed length, and this seemed not to disturb Access 2003 at all, but did really come through with full force in Access 2010. I'll have to check all my 60-odd tables before continuing...
So, there remains only one question now, the one about the progress bar :-)
Regards
Bernard
Thanks for answers. I know I asked 3 questions in one post, and there is a reason to that: I am currently on a short holiday in Sweden in a place where there is no land line and virtually no GSM reception, so the Internet down/upload speeds to my USB modem-equipped laptop are measured in double-digits kbps, typically in the 20 to 30 kbps (!), so every post takes ages and is a real torture with the current fancy web sites like the EE site. That's why I packed all in one post.
Yes, it's a 64 bit machine adn Office 2010 64-bit.
What are the "native methods" of showing a progress bar ? Can you be more specific ?
I found the problem on the text and combo boxes. It was my fault. Some of the fields in the DB were wrongly defined with fixed length, and this seemed not to disturb Access 2003 at all, but did really come through with full force in Access 2010. I'll have to check all my 60-odd tables before continuing...
So, there remains only one question now, the one about the progress bar :-)
Regards
Bernard
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
However:
Is this a 64 bit machine, running 64 bit Office? If so, then you can't use the ActiveX controls you mention (and you shouldn't be using them in access anyway, since they're not built for that platform). Instead, use one of the "native" methods of showing a Progress bar.
Is this a Bound form application (i.e. you have a Recordsource for the Form, and a ControlSource for your controls)?