cmd-Button doesn't react

[Bert Leu]

Hi

A cmd-Button, which did well for years, makes problems in a XP Pro SP2 -
environment (Access 2000).

The DB itself is ok.

Re-Installing Office 2000 doesn't save this problem. Any idea?

Thanks
Bert Leu

 

[Nikos Yannacopoulos]

Bert,

This is as good as telling your mechanic your car idn't functioning
properly! Post the error message, the code behind the button, and the
line it occurs on.

Nikos

 

[Bert Leu]

Hi Nikos

I understand your idea. But in my opinion the code (or the line) doesn't
matter, because that code will not be run (debugging: nothing happens).

 

[Nikos Yannacopoulos]

Bert,

If you are certain that the event doesn't fire, the only possible reason
that I can think of is that, although the code still exists in the
form's module, the reference to it has been deleted from the command
button's Click property. To check, open the form in design view, select
hte button, dislay the Properties window, select tab Events and look if
there is an entry like [Event Procedure] nect to On Click; my guess is
it's not there. Put the corsor in the poperty box and click on the small
button with the ellipsis sign that appears on the right, and select Code
Builder; you will be taken to the VBA editor where, hopefully, the code
is sthill there. Return to the form design and save. problem should be
solved.

HTH,
Nikos

 

[Bert Leu]

Hi Nikos

Thank for your advice. Again I understand what you mean. But: The same DB,
placed on another PC works well! So, the problem must lie in the Access- or
BS-Software..

Bert,

If you are certain that the event doesn't fire, the only possible reason
that I can think of is that, although the code still exists in the
form's module, the reference to it has been deleted from the command
button's Click property. To check, open the form in design view, select
hte button, dislay the Properties window, select tab Events and look if
there is an entry like [Event Procedure] nect to On Click; my guess is
it's not there. Put the corsor in the poperty box and click on the small
button with the ellipsis sign that appears on the right, and select Code
Builder; you will be taken to the VBA editor where, hopefully, the code
is sthill there. Return to the form design and save. problem should be
solved.

HTH,
Nikos

Hi Nikos

I understand your idea. But in my opinion the code (or the line) doesn't
matter, because that code will not be run (debugging: nothing happens).

 

[Nikos Yannacopoulos]

Sorry, no more ideas.

Nikos

Hi Nikos

Thank for your advice. Again I understand what you mean. But: The same DB,
placed on another PC works well! So, the problem must lie in the Access- or
BS-Software..

Bert,

If you are certain that the event doesn't fire, the only possible reason
that I can think of is that, although the code still exists in the
form's module, the reference to it has been deleted from the command
button's Click property. To check, open the form in design view, select
hte button, dislay the Properties window, select tab Events and look if
there is an entry like [Event Procedure] nect to On Click; my guess is
it's not there. Put the corsor in the poperty box and click on the small
button with the ellipsis sign that appears on the right, and select Code
Builder; you will be taken to the VBA editor where, hopefully, the code
is sthill there. Return to the form design and save. problem should be
solved.

HTH,
Nikos

Hi Nikos

I understand your idea. But in my opinion the code (or the line) doesn't
matter, because that code will not be run (debugging: nothing happens).



"Nikos Yannacopoulos" <[email protected]> schrieb im

Newsbeitrag

Bert,

This is as good as telling your mechanic your car idn't functioning
properly! Post the error message, the code behind the button, and the
line it occurs on.

Nikos

Bert Leu wrote:


Hi

A cmd-Button, which did well for years, makes problems in a XP Pro

SP2 -

 

[Bert Leu]

Hi Nikos

Thanks for your support. In the meantime I found the error. Due to the fact,
that I've a lot of serious Problems on my new notebook, I thought, that the
cause of the Access-Problem resides in supernatural forces too. But the
cause was, that a VB-DLL was not referenced in Access on the new Comp.

Thanks and sorry..

Sorry, no more ideas.

Nikos

Hi Nikos

Thank for your advice. Again I understand what you mean. But: The same DB,
placed on another PC works well! So, the problem must lie in the Access- or
BS-Software..

Bert,

If you are certain that the event doesn't fire, the only possible reason
that I can think of is that, although the code still exists in the
form's module, the reference to it has been deleted from the command
button's Click property. To check, open the form in design view, select
hte button, dislay the Properties window, select tab Events and look if
there is an entry like [Event Procedure] nect to On Click; my guess is
it's not there. Put the corsor in the poperty box and click on the small
button with the ellipsis sign that appears on the right, and select Code
Builder; you will be taken to the VBA editor where, hopefully, the code
is sthill there. Return to the form design and save. problem should be
solved.

HTH,
Nikos

Bert Leu wrote:

Hi Nikos

I understand your idea. But in my opinion the code (or the line) doesn't
matter, because that code will not be run (debugging: nothing happens).



Newsbeitrag



Bert,

This is as good as telling your mechanic your car idn't functioning
properly! Post the error message, the code behind the button, and the
line it occurs on.

Nikos

Bert Leu wrote:


Hi

A cmd-Button, which did well for years, makes problems in a XP Pro

SP2 -

environment (Access 2000).

The DB itself is ok.

Re-Installing Office 2000 doesn't save this problem. Any idea?

Thanks
Bert Leu