Next New Issue - Manipulating a standalone Label to change the text

[Welshgasman]

but I'm sure something will still cause me a problem

More than likely, but there is a huge difference in help found for VBA as opposed to Macros.

[Micron]

Use converted macros for guidance where you pick up clues that you research, but some of the converted code is what I would call verbal diarrhea. So don't adopt too much of its format or style.

[ScubaBart]

Use converted macros for guidance where you pick up clues that you research, but some of the converted code is what I would call verbal diarrhea. So don't adopt too much of its format or style.

Well, That doesn't give me a warm fuzzy feeling.

[Welshgasman]

It would be the same if you recorded an Excel macro.

However it will still work I expect, just do not use the converted code as learning examples entirely.

[Welshgasman]

Look at it this way.
If I suddenly decided I wanted to raise bees, and joined a bees forum, there are likely ready made hives that I could buy at a premium, but you would tell me, you don' need this, you don't need that etc.

[moke123]

Using VBA your requirement is very simple.

In the load event of the form:

If Me.NewRecord then
     'set your labels for new records
  else
     'set you labels for editing
end if

[moke123]

Well, That doesn't give me a warm fuzzy feeling.

I think what Micron is referring to is the extra stuff that converting adds to the code that isn't necessarily needed.

for instance the VBA:

Private Sub Command140_Click()
  DoCmd.OpenForm  "Form1", , , , acEdit
End Sub

when converted from a macro :

'------------------------------------------------------------
' Command140_Click
'
'------------------------------------------------------------
Private Sub Command140_Click()
On Error GoTo Command140_Click_Err


    DoCmd.OpenForm "Form1", acNormal, "", "", acEdit, acNormal




Command140_Click_Exit:
    Exit Sub


Command140_Click_Err:
    MsgBox Error$
    Resume Command140_Click_Exit


End Sub

[Micron]

I have no issue with error handlers such as in that converted code. In fact, if you modify application settings I consider them necessary. For me the converted code isn't great for learning how to concisely name variables or line labels and I suspect it would never set Option Explicit either. Besides, you'll never be able to do many things with vba if all you learn from is converted code, because many things can't be done with those macros in the first place. That last point would be my major one. Or maybe it would be the fact that when a macro bombs out there is no recovering from it (at least there wasn't when I stopped using them long ago).

[ano]

ur a great teacher micron like my french teacher discourage is not the way to support vba has many search result and macro seems not