On <event> Error

[Guest]

My database was getting too big and running too slow from adding and deleting
objects. So, I created a new database, then imported all of the old one's
objects. It increased in speed and reduce in size significantly. But, all
of the command buttons, or any procedure call event, errored when
clicked/activated stating that the On <event> argument was the source of the
problem. none of the control names were changed in the process.
Any clues?
Thanks,
Trent Argante
[DC.J(71)!(365)]

 

[Van T. Dinh]

You may have some MISSING References.

Open the VBE (code window) and use the Menu Tools / References ... and check
if you have any missing References.

See Douglas J. Steele's article:

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

 

[Guest]

Thanks, Van; that worked. But, now I'm confused: There was a missing
reference - a reference to a DLL that I wrote in VB6. So, why would a
reference to a user-defined DLL cause standard control-to-event-handler
operations to fail?
--
Trent Argante
[DC.J(71)!(365)]

You may have some MISSING References.

Open the VBE (code window) and use the Menu Tools / References ... and check
if you have any missing References.

See Douglas J. Steele's article:

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

--
HTH
Van T. Dinh
MVP (Access)

My database was getting too big and running too slow from adding and
deleting
objects. So, I created a new database, then imported all of the old one's
objects. It increased in speed and reduce in size significantly. But,
all
of the command buttons, or any procedure call event, errored when
clicked/activated stating that the On <event> argument was the source of
the
problem. none of the control names were changed in the process.
Any clues?
Thanks,
Trent Argante
[DC.J(71)!(365)]

 

[Van T. Dinh]

Sorry ... don't know why but this has been the behaviour in Access for quite
a while now.

--
HTH
Van T. Dinh
MVP (Access)

Thanks, Van; that worked. But, now I'm confused: There was a missing
reference - a reference to a DLL that I wrote in VB6. So, why would a
reference to a user-defined DLL cause standard control-to-event-handler
operations to fail?
--
Trent Argante
[DC.J(71)!(365)]

You may have some MISSING References.

Open the VBE (code window) and use the Menu Tools / References ... and
check
if you have any missing References.

See Douglas J. Steele's article:

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

--
HTH
Van T. Dinh
MVP (Access)

My database was getting too big and running too slow from adding and
deleting
objects. So, I created a new database, then imported all of the old
one's
objects. It increased in speed and reduce in size significantly. But,
all
of the command buttons, or any procedure call event, errored when
clicked/activated stating that the On <event> argument was the source
of
the
problem. none of the control names were changed in the process.
Any clues?
Thanks,
Trent Argante
[DC.J(71)!(365)]

 

[Guest]

Van, thanks. I can accept this "answer" =;O)
I read the article from
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html
but most of it was over my head. I'm one of those guys who can do a lot
more than I understand - it gets quite frustrating at times. There were
parts that were helpful though, so I appreciate the ref.
--
Trent Argante
[DC.J(71)!(365)]

Sorry ... don't know why but this has been the behaviour in Access for quite
a while now.

--
HTH
Van T. Dinh
MVP (Access)

Thanks, Van; that worked. But, now I'm confused: There was a missing
reference - a reference to a DLL that I wrote in VB6. So, why would a
reference to a user-defined DLL cause standard control-to-event-handler
operations to fail?
--
Trent Argante
[DC.J(71)!(365)]

You may have some MISSING References.

Open the VBE (code window) and use the Menu Tools / References ... and
check
if you have any missing References.

See Douglas J. Steele's article:

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

--
HTH
Van T. Dinh
MVP (Access)


My database was getting too big and running too slow from adding and
deleting
objects. So, I created a new database, then imported all of the old
one's
objects. It increased in speed and reduce in size significantly. But,
all
of the command buttons, or any procedure call event, errored when
clicked/activated stating that the On <event> argument was the source
of
the
problem. none of the control names were changed in the process.
Any clues?
Thanks,
Trent Argante
[DC.J(71)!(365)]

 

[Douglas J. Steele]

References are like apples: one bad one can spoil the whole bunch.

Essentially, Access has to look in the referenced files for certain
functions. If when it's searching, it finds a broken reference, Access will
raise an error, even if the function it needs is in a library where the
reference isn't broken.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Thanks, Van; that worked. But, now I'm confused: There was a missing
reference - a reference to a DLL that I wrote in VB6. So, why would a
reference to a user-defined DLL cause standard control-to-event-handler
operations to fail?
--
Trent Argante
[DC.J(71)!(365)]

You may have some MISSING References.

Open the VBE (code window) and use the Menu Tools / References ... and
check
if you have any missing References.

See Douglas J. Steele's article:

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

--
HTH
Van T. Dinh
MVP (Access)

My database was getting too big and running too slow from adding and
deleting
objects. So, I created a new database, then imported all of the old
one's
objects. It increased in speed and reduce in size significantly. But,
all
of the command buttons, or any procedure call event, errored when
clicked/activated stating that the On <event> argument was the source
of
the
problem. none of the control names were changed in the process.
Any clues?
Thanks,
Trent Argante
[DC.J(71)!(365)]