larrytxeast
New member
- Local time
- Today, 14:32
- Joined
- Sep 5, 2015
- Messages
- 7
This is my first post to this forum, I am coming here as I've designed databases before in Access, although that skill has been dormant in me for sometime, and a friend has asked for my help. I mostly used Access 97 and XP, between 2000 and 2003, for various different small companies on a small level (as in maybe 5 people used the database total), although for a brief bit in 2010 I used Access 2007 for a different employer.
My skill level--I have taken no classes in this, I'm self taught. I advanced to the point of learning about doing some basic VBA, commands such as DoCmd.Close and the like, for buttons in forms in "design" view. I also managed to create code that dynamically created SQL code on a form for searching records, based on what the user entered in the text boxes before pressing "Search." To a certain degree I also created "modules" of code which I could "call up" in code.
I've probably forgotten 90% or more of all of this due to being "dormant" in this for awhile, although I in fact had gotten to the point of making simple web pages of my own where I'd document code and instructions on how to do things and the like. If I dig up those pages (some of them were published and "live," and regardless they're saved on a DVD somewhere as HTML files), I'd probably managed to remember much of all of this.
I forget what source I used, but it was the source where you have naming conventions for consistency, tables were named "tblContacts" forms were "frmContacts" a command button on a form had a "control" name of "cmdExit" for, example, the button on the form which would close the form. (I'd disable the built-in X on the form and create my own button for that, as well as buttons for adding and deleting records, etc, as well as buttons that would print the report.) I knew how to "right-click" on the button in "design" view, select "build code" and then type in "DoCmd.OpenForm "" " and so on.
I never held any sort of high level position with this, mostly I would be hired on at a company in a clerical/administrative capacity, hired to deal with whatever crummy database someone else had thrown together prior to me (often times they even lacked forms), but I learned all of this on my own via newsgroups or books and then I would end up "jazzing up" the database to a ridiculously high level--for a clerical person. I never "broke through" to the point of being hired in the capacity of a IS or IT Tech person, though, I somewhat stopped "applying myself" as it were.
I post today because I'm back at it again briefly for a friend, one whom I worked with back when I first started doing this, and I'm trying to "clear out the cobwebs" in my head to get going again. I am using Access 2010 on a laptop I purchased for $50 last month, and it's making my head swim even doing basic things such as resizing a control in a form. So expect to see a lot of posts of this type where I try to "clear out the cobwebs" and figure out what I'm doing in Access 2010 the things I used to do in Access 2002/XP.
My skill level--I have taken no classes in this, I'm self taught. I advanced to the point of learning about doing some basic VBA, commands such as DoCmd.Close and the like, for buttons in forms in "design" view. I also managed to create code that dynamically created SQL code on a form for searching records, based on what the user entered in the text boxes before pressing "Search." To a certain degree I also created "modules" of code which I could "call up" in code.
I've probably forgotten 90% or more of all of this due to being "dormant" in this for awhile, although I in fact had gotten to the point of making simple web pages of my own where I'd document code and instructions on how to do things and the like. If I dig up those pages (some of them were published and "live," and regardless they're saved on a DVD somewhere as HTML files), I'd probably managed to remember much of all of this.
I forget what source I used, but it was the source where you have naming conventions for consistency, tables were named "tblContacts" forms were "frmContacts" a command button on a form had a "control" name of "cmdExit" for, example, the button on the form which would close the form. (I'd disable the built-in X on the form and create my own button for that, as well as buttons for adding and deleting records, etc, as well as buttons that would print the report.) I knew how to "right-click" on the button in "design" view, select "build code" and then type in "DoCmd.OpenForm "" " and so on.
I never held any sort of high level position with this, mostly I would be hired on at a company in a clerical/administrative capacity, hired to deal with whatever crummy database someone else had thrown together prior to me (often times they even lacked forms), but I learned all of this on my own via newsgroups or books and then I would end up "jazzing up" the database to a ridiculously high level--for a clerical person. I never "broke through" to the point of being hired in the capacity of a IS or IT Tech person, though, I somewhat stopped "applying myself" as it were.
I post today because I'm back at it again briefly for a friend, one whom I worked with back when I first started doing this, and I'm trying to "clear out the cobwebs" in my head to get going again. I am using Access 2010 on a laptop I purchased for $50 last month, and it's making my head swim even doing basic things such as resizing a control in a form. So expect to see a lot of posts of this type where I try to "clear out the cobwebs" and figure out what I'm doing in Access 2010 the things I used to do in Access 2002/XP.
Last edited:
