When to use modules?

[Paowtrick]

First of im a beginner.
So ive been building a DB for a while now, and start to notice some codes I have to type over and over again. Some places i have 6-7 rows of code in three places on the same form. So it starts to build up unnecessary much. So I read about modules, and I think that they are possible to store repeating codes and call them when I need? So if anyone could help me keep a cleaner code.

And I appreciate if any one knows a good forumpost or article or youtube clip I should check out to learn some more about good structure, to make it "future proof".

[ranman256]

i separate my functions,
modFilesys has all my file functions; MakeDir, DoesFileExist...etc
modGLOBE has all my global definitions
modUSER has all user operations; getUserID, getUserName, etc
modAPP used for custom ops for the app itself. Usu different for every app.

it just lets me find things easier.

[Minty]

In addition to Ranmans suggestions for storing globally used functions, If the code you refer to is very form specific you can create a Private Sub in the forms code module, and call it repeatedly whenever you need it rather than repeating it. e.g. lets say you needed something like this very simplified example to run on lots of different events;

Private Sub SetButtonsUp()        
   Me.txtBox1.Visible = False
   Me.txtBox2.Visible = False
   Me.txtBox3.Visible = True
   Me.txtBox4.Visible = True


End Sub

Then simply in all the places you want to use it on the form ;

Call SetButtonsUp

[Paowtrick]

uff, I feel like I need to read up ALOT more, I did not understand any of the functions
I will try that call thing out though.

edit: is this something to have as a function

If Dirty = True Then Dirty = False
and then use call dirty?

[ranman256]

I erase all the ISDIRTY code.
its of no use and not backwards compatible.

[Paowtrick]

oh, I use isdirty on every single "after update" to get the results of the change. Should I do something else?

[ssanfu]

The "Dirty" property is an indication if there are unsaved changes to a form. (NOT the form design - just data!)

Nothing wrong with using it.
In my code, I use this

If Me.Dirty Then 
  Me.Dirty = False
End If

[pbaldy]

I erase all the ISDIRTY code.
its of no use and not backwards compatible.

I'm also curious about this. I use the same code Steve does, though for me it's a very rare case of me using one-line format:

If Me.Dirty Then Me.Dirty = False