Error on VBA code Compilation

[Lou_Reed]

Okay, first things first. What is the form and it associated code where the compile fails? Is it

frmEditPropass and frmNewProperty?

in the db that compiles, the is where I find the line:

Forms!sfrmPropertyPass1.updateButtons

So it must fail (in the db that fails) on those two forms' VBA code. Obviously, only one can fail first, but that is where the code (Forms!sfrmPropertyPass1.updateButtons) is on those two forms.

Any help appreciated. Thanks in advance.

Respectfully,

Lou_Reed

[Lou_Reed]

There was a code difference in the recent db's. In the previous one you had:

updateButtons

to call the function from another form, in the latest it was:

Forms!sfrmPropertyPass1.updateButtons

The first threw the compile error, the second won't.

Okay, on the db that fails where is the code line

updateButtons

on what form's code? In the db that does not fail where is the line:

Forms!sfrmPropertyPass1.updateButtons

I mention this because the failure of the code line

updateButtons

is associated with frm_Personnel.

Also, in the form that fails both frmEditProperty and NewProperty.

Have thew line:

Forms!sfrmPropertyPass1.updateButtons

near the bottom in the Sub btnSaveRecord_click. For the db that fails that is the only instances where they are. They are nowhere else.

Now those two forms and their code are the same for both db (the one that works and the one that fails)..

In the db that works where is additional instance of the line Forms!sfrmPropertyPass1.updateButtons? That is only in the db that works and not the db that fails it is missing.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[CodeLiftSleep]

Okay, but again to what purpose does the phrase "Cancel as Integer" serve?

When I added that to the code I got a new error, but an error nonetheless

The modified db and the pdf file are attached. How to remove this error.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

It doesn't matter what purpose it serves, that is the signature needed to use that method properly.

[Lou_Reed]

There was a code difference in the recent db's. In the previous one you had:

updateButtons

to call the function from another form, in the latest it was:



Forms!sfrmPropertyPass1.updateButtons

The first threw the compile error, the second won't.

Forms!sfrmPropertyPass1.updateButtons

Where is this line in the db whose VBA code complies and what is in its place in the db whose VBA code does not compile?

I think it is as basic as I can make it. Sorry about the palaver above.

Respectfully,

Lou Reed

[Lou_Reed]

Okay, I think that I see the error. In the db whose VBA code compiles there is an abbreviated frmPersonnel. Several Subs and Functions are missing including the one that contains
updateButtons.

So obviously it compiles with no problem; upodateButtons is missing. In the db whose VBA code fails to compile the frmPersonnel is much larger with many more subs and functions; including the one that contains update buttons.

The way to fix this is to put a definition sub or function for update buttons in the frmPersonnel.

If there is another easier way, please tell me.

Respectfully.

Lou Reed

[pbaldy]

I don't have the big picture of what you're trying to accomplish. If it will always refer to the same form/subform, you can change the "Me" references to the full reference "Forms!FormName.SubFormName.Form.ControlName" and put the function in a standard module. Then you can just call it with the function name from anywhere.

[Lou_Reed]

This question may be off base, but I will ask it anyway. I have looked on the internet for a list of known problems that arise when one translates an MS macro to its corresponding VBA code. I have found many, most with the timely and accurate help from many experts on the MS Access Forums.

However, I was wondering if there is any list or tech-report that lists all or most known inconsistencies. I have not found one on the internet, but I have not looked everywhere.

It would help to if there were such a list.

Is there and where might I locate it?

Any help appreciated. Thanks in advance.


Respectfully,


Lou Reed

[Lou_Reed]

It would be helpful if someone could answer the question in Post # 22. There must some compiled list like that,
that shows the obvious errors when an Access macro is converted to VBA code.

Any help appreciated. Thanks in advance.


Respectfully,


Lou Reed

[pbaldy]

I didn't answer because I'm not aware of such a list. I'd guess the lack of responses indicates nobody else is either.

[Lou_Reed]

Okay, thanks for the effort. I just thought that there had to be one somewhere. It seems to be a systemic prpbelkm when you convert Access macros to VBA code.

Thanks again.

Respectfully,

Lou Reed

[pbaldy]

To be honest, I don't know that it's used that much. It's a handy learning tool, but I doubt much production code gets written that way.