ActiveX Error; please explain!

[Guest]

When a subform loads, it runs a module using the system date. It has worked
without flaw for several years. Now it fails. I discover that one of my
"available references" is missing: "DatePicker ActiveX Control module" in
C:\Novell\Groupwise\GWDPK.OCX! The university recently switched to a
different email client and got rid of GroupWise. (And good riddance, it
was...)

1) What on Earth did I do to make my Access database depend on a GroupWise
control?
2) What do I do now to get my system date back?

Please help on this, as I obviously don't understand something fundamental!

Thanks.

 

[Michel Walsh]

Hi,


If you don't use that reference, UNCHECK it...


Maybe it is needed by a subroutine (or was needed) which is not used (very
often) anymore. In VBE, Tool | Compile yourDatabase should tell you, with
an error, if that library is still required, and WHERE (in which line of
code), once you unchecked it. It is up to you how to repair your code, if
that occurs. If not, you can assume the reference was not really required.


Hoping it may help,
Vanderghast, Access MVP

 

[Dirk Goldgar]

When a subform loads, it runs a module using the system date. It has
worked without flaw for several years. Now it fails. I discover
that one of my "available references" is missing: "DatePicker ActiveX
Control module" in C:\Novell\Groupwise\GWDPK.OCX! The university
recently switched to a different email client and got rid of
GroupWise. (And good riddance, it was...)

1) What on Earth did I do to make my Access database depend on a
GroupWise control?

Can't help you with that one. Maybe you added that control to a form,
then later removed it.

2) What do I do now to get my system date back?

Please help on this, as I obviously don't understand something
fundamental!

I'm not sure what you mean by "using the system date". If you meant
that references to the VBA Date() function are failing, it could well be
because of the broken reference to the GroupWise control. That broken
reference could be interfering with Access's ability to resolve other
references -- VBA always seems to be the first one to take the hit in
these cases.

Try removing the missing reference and then recompiling your database.
If that reference was really needed, you should get an error that
highlights where it was used. If you don't get an error, maybe your
troubles will be over.

 

[Guest]

Thanks for your feedback. Yes, by "system date" I did mean the VBA Date()
function. The fix turned out to be simply un-checking that item in the
reference list. I guess Access just went to another reference and the code
is now OK. I'll recompile to be sure.

I still don't know how that reference got in there, but there was a period
when I was attempting to send a bulk-email from an MS Word merge through
GroupWise. The data for the merge was in this Access dbf, and maybe
something got connected oddly. I'll blame it on GroupWise, since it behaves
like a stubborn child anyway.

Thanks again.