Update Acc. V2 with A_MENU_VER1X

  • Thread starter Thread starter Luprix
  • Start date Start date
L

Luprix

Escuse my bad english.

Upgrading Acc. V2 to 2K.
I need update lines with the old sintax:

DoCmd.DoMenuItem 0, 1, 1, A_MENU_VER1X
DoCmd.DoMenuItem 0, 1, 6, A_MENU_VER1X
DoCmd.DoMenuItem 0, 1, 7, A_MENU_VER1X
DoCmd.DoMenuItem 0, 3, 2, A_MENU_VER1X
DoCmd.DoMenuItem 7, 2, 0, A_MENU_VER1X
DoCmd.DoMenuItem 0, 0, 4, A_MENU_VER1X

Not all values relationed in object explorer.
Not search find in Internet, for Nº of Macros V 1.

Regards for all.

Luprix.
 
This code should run under A2K, if you use the constant acMenuVer1X instead
of the older version.
You can also leave this constant off completely, as it is the default.

However, I would suggest that you figure out what this code is doing and use
the appropriate
DoCmd.RunCommand constant.
That will make it much easier for people who come after you to maintain your
code.

HTH
- Turtle
 
Thanks MacDermott.
However, I would suggest that you figure out what this code is doing and use
the appropriate
DoCmd.RunCommand constant.

that is what I try to carry out, but... Which is the RunCommand of those
lines?
I can approach by means of the analysis of the routines. But I cannot be
sure without knowing the macros that execute those lines exactly.
Each value numeric correxponde with the nº of order of macros generator
based on zero. Certain values don't have relation with intrinsic constants.
Example: "DoMenuItem 7, 2, 0", Report ..... what?
I don't have Access 1.

Can you help me?

Regards.
 
I don't have v.1 either, so I can't tell you exactly what each command
means.
However, you can learn a lot by trial and error.
For example, if you type this into the immediate window:
DoCmd.DoMenuItem 0, 1, 1, acMenuVer1X
you will get a messagebox telling you it can't execute the "Undo" command at
this time.
That's a pretty good indication that this could be replaced by
DoCmd.RunCommand acCmdUndo

HTH
- Turtle
 
Back
Top