Location of ActiveX controls?

[Christine Pearc]

I use the Active X calendar control 10.0 in a number of forms*. The mscal.ocx file is in c:\Program Files\Microsoft Office\Office 10.

(*In the calendar's Properties it says it is "MSCAL.Calendar.7", which I think is just MS's way of confusing people.)

After splitting the deploying my app, it appears lots of my users either don't have version 10.0 or it is stored someplace else; for example, in C:\Windows\System32. Because they don't have the correct version/path, everything crashes.

So, how can I easily determine whether users have the right ActiveX in the correct location?

The Microsoft web site says "To distribute your component as part of a Visual Basic application, you can use Package and Deployment Wizard". I don't have that wizard in my version of Access (2002 SP3 on Windows XP), so that's not an option.

Microsoft also says to "To enter the base address for your component, open the Project Properties dialog box and select the Compile tab. The address is entered in the DLL Base Address box, as an unsigned decimal or hexadecimal integer. The default value is &H11000000 (285,212,672). If you neglect to change this value, your component will conflict with every other in-process component compiled using the default. Staying well away from this address is recommended." It seems to make sense that I put the mscal.ocx in the database's directory on the server to serve as the "base address", but other than that this option scares the heck out of me.

Does someone have any suggestions how to easily ensure users have the right ActiveX version on their computer - and in the correct location? (I'm not a super-coder.)

As always, thanks
Christine

 

[ghudson]

Another reason to avoid ActiveX controls.

You could use a custom Access calendar that will allow the user to select a date and/or time. This excellent sample will do just that. Popup Calendar - Version 3

You have to be a member [membership is free] of the UtterAccess forum to download the samples from their code archives section of the forum.

 

[Christine Pearc]

Yikes, that's a heck of alot of code in the pop-up calendar! I'd have to modify it to suit my needs (if I can figure it out!), especially since some forms have up to 3 fields that you the calendar function, along with modifying all my forms! Still, the ability to show 3 months is a really nice feature that might be worth it. I'll have to poll all our users to see how big the problem is and how much effort can be justified.

Microsoft/Access never ceases to amaze and confound me. You would think they would tell you about the limitations of ActiveX right up-front, instead of having to find out about this sort of thing after the fact - and then giving confusing instructions like what I found after a lengthly search for info. Better still, since Access by default is set up for multi-users, you'd think they would have included the functionality to compile/gather all the bits that make up an application. Sigh.

Thanks, ghudson. If any one else has another solutions, they would be most welcome.

Christine

 

[ghudson]

You should not have to make that many changes. You can try the authors first calendar if you do not want the fancy three months options. Here is the link to that one... Popup Calendar