Microsoft Date & Time Picker 6.0 (SP4) Problem in XP


I have created and tested a calendar form using Microsoft Date & Time Picker 6.0 (SP4) using Access 2007 in a Vista machine. This front-end is used by users of machines running Vista and XP. Those using Vista are OK. Those using XP I have a problem. The OCX displays correctly but:
1) does not show the date set
2) when the user tries do do anything on the control a message comes saying something like: "The expession OnClick generated the following error: the events are not supported by the object or class"

I  have already checked and the references are OK. I have tried to repair Office 2007 with no result. It seems to be an issue with XP.

Do you have any ideas or suggestions?

Thank you,

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey CoachmanMIS LiasonCommented:

Did you try using the standard Calendar control?
(Calendar Control 12.0?)

Or... one of the third party calendar controls:

Jeffrey CoachmanMIS LiasonCommented:



You never replyed to my post?
mbertuolAuthor Commented:
If I ask for a solution for a problem I have I will not switch to another product or control. It is not a solution.
Jeffrey CoachmanMIS LiasonCommented:

Fair enough...
However, you did not make it clear that switching to another product or control was not an option.
I was merely trying to help.

If you asked: "How do I add records to a table?" and I said: "Use an DAO recordset"...
You could say "I cant use DAO, I must use ADO".
... again I have no way of knowing what is, or is not, acceptable, if you don't tell me.
I was only offering to you the solution that worked for me.

<It is not a solution>
Well it is a solution, it was just not within your parameters. (Like my ADO/DAO example)
Using a third party date control is a common accepted solution to these types of compatibility issues, see here:

You said:
<Do you have any ideas or suggestions?>
That was my "Idea/Suggestion".
Or did I read your post incorrectly?

In any even, now that you have defined your parameters, here is what Microsoft has stated as the only solutions for your error:
Method 1
Keep only one version of Access on the computer. To do this, you must uninstall Access 2007 or Access 2003. For more information about this method, see the "More information" section.
Method 2
Run the Msaccess.exe file by using the Run As Administrator option. For more information about how to run the file by using this option, click the following article number to view the article in the Microsoft Knowledge Base:
922708 ( How to use User Account Control (UAC) in Windows Vista
Method 3
Delete the Msacc.olb file for Access 2003. Then, repair the Access 2003 installation.

Now, this is straight from MS.
Give them a try.
One of them should work for you, If not, then I am afraid the answer is:
"This cant be done".

Sorry for any mis-understanding


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jeffrey CoachmanMIS LiasonCommented:
Glad I could help

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.