...what about calling it? You gave me all of these modules and what I am really trying to do is give a tool kit ot myself and my people...

What we're talking about developing is an Application Programming Interface -- a standardized manner of accessing particular data and effecting actions upon it. I described a model in which you could use (a mere) two modules, one of which to be used by your fellow programmers directly (the 'User' module), and the other that only you need to be concerned with directly ('UserDBConn').

Now I want to provide a set of functions ... to access that database but not from cutting and pasting the files into each script as they are written.

And modules are clearly a good way to do this. If you need to modify behavior in some way, say with openning the DB connection, you simply change the code in UserDBConn and release that mod to your fellow developers. Their code doesn't have to change a bit.

HTH, fever