Unavailable reference libraries

[Guest]

I am a novice, but have managed to create an Access Db for multiple users that’s been working well for a couple of months (largely thanks to you all and this user forum)

When making a recent upgrade, users are getting some unexplainable occurrences that I believe relate to the reference library. I am running XP and Access v2002, users are running the same

I believe the first relates to my use of the Lebans calendar; downloaded and integrated into VB.
When I view my library references, I have one entitled ‘Microsoft Calendar Control 10.0’. They do not have it checked, or included as an option in the library reference list. My inclination is to email the ‘MSCAL.OCX’ file to them and have them place it in the same folder as I have – but I don’t want to create any problems. I have no idea what this file does, or whether I might overwrite a file of theirs with the same name? Is the ‘MSCAL.OCX’ file an element of Lebans calendar? If I load it on their PCs, will it appear in the reference library

Second
Users have a MS DAO 3.51, whereas my PC has DAO 3.6. How can I get them to 3.6? Is it necessary

Last
I have a reference entitled, ‘Microsoft Office XP Web Components.†Despite that users are running XP, they don’t have this reference within their libraries

Starting to get in over my head. Any suggestions would be appreciated

 

[Douglas J. Steele]

One of the great advantages of Stephen's calendar is that it doesn't require
any OCXs. If you're using his calendar, uncheck the Microsoft Calendar
Control 10.0 on your machine.

I can't think of any reason why users running Access 2002 would have a
reference to DAO 3.51: it's not included as part of Office XP!

Are you using Microsoft Office XP Web Components? What happens if you
uncheck it on your machine?

My standard advice is to "starve" your references: only have the bare
minimum. To determine whether or not you need a particular reference,
uncheck it and compile your application. If it doesn't complain, you likely
didn't need the reference.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

I am a novice, but have managed to create an Access Db for multiple users

that's been working well for a couple of months (largely thanks to you all
and this user forum).

When making a recent upgrade, users are getting some unexplainable

occurrences that I believe relate to the reference library. I am running XP
and Access v2002, users are running the same.

I believe the first relates to my use of the Lebans calendar; downloaded and integrated into VB.
When I view my library references, I have one entitled 'Microsoft Calendar

Control 10.0'. They do not have it checked, or included as an option in the
library reference list. My inclination is to email the 'MSCAL.OCX' file to
them and have them place it in the same folder as I have - but I don't want
to create any problems. I have no idea what this file does, or whether I
might overwrite a file of theirs with the same name? Is the 'MSCAL.OCX'
file an element of Lebans calendar? If I load it on their PCs, will it
appear in the reference library?

Second,
Users have a MS DAO 3.51, whereas my PC has DAO 3.6. How can I get them to 3.6? Is it necessary?

Last,
I have a reference entitled, 'Microsoft Office XP Web Components."

Despite that users are running XP, they don't have this reference within
their libraries.