kousotsu
Eeny, meeny, miney...Jim?
- Local time
- Today, 17:21
- Joined
- Apr 2, 2004
- Messages
- 23
Rtm?
While the forums are great for help, there are some of your questions that are easily answered by searching through the Access help files. The reading isn't all that intensive, and you seem like a smart enough cookie to catch on. I would recommend diving into the VBA help (using code in forms and such) headfirst. I only say this because it REALLY helped me back into the VBA swing. (I think Pat suggested it to me way back in March/April ^_^).
For instance, about the question of auto-closing the update form after a messagebox: in design view, right-click any item and click the "properties" selection. This will bring up the properties dialog. Using the object selection dropdown, find an object like a textbox or the form itself - essentially anything that looks manipulable by the user - and select the "Events" tab. Here, you'll find the various actions attributed to this form element (ie: beforeUpdate, onClick, etc). If you want a confirmation for the update first, follow this process:
· select your command button, open the properties dialog.
· select the "other" tab, and name the button according to conventions (cmd<WhatItDoes>).
· select the event tab, find "onClick" (when you focus on this element, a small button with an ellipsis will appear to the right - you can use this or the drop down to select "[Event Procedure]" - which you will use to open the code window.
· look up in Access Help how to use Y/N message boxes as a starting point for data operations - they're great for deciding simple cases (if yes, do this; if no, don't do this).
Then (provided you want the form to close regardless of what they click), in the end of each selection's code you'll put a line with a command ("DoCmd." element) that tells that particular form to close itself.
Once you start learning the VBA code this way, you'll be able to intuitively answer a lot of these questions on your own. I started doing that, and it's really helped me a great deal - Pat will tell you, I was really at a loss there in March/April. ^_^
Just my two bits on how to be successful with Access. The forums are great, but there are a LOT of duplicate questions floating around. You're not dumb, for the record - my boss is dumb. At least you understand the value of Access and the value of well placed questions. ^_^
The other thing that really helped me was the deprecated Object Model for Access. Hey, Pat - do you have a link to that somewhere? I can't find one, and the one I have isn't on my office machine.
Cheers!
- Z
While the forums are great for help, there are some of your questions that are easily answered by searching through the Access help files. The reading isn't all that intensive, and you seem like a smart enough cookie to catch on. I would recommend diving into the VBA help (using code in forms and such) headfirst. I only say this because it REALLY helped me back into the VBA swing. (I think Pat suggested it to me way back in March/April ^_^).
For instance, about the question of auto-closing the update form after a messagebox: in design view, right-click any item and click the "properties" selection. This will bring up the properties dialog. Using the object selection dropdown, find an object like a textbox or the form itself - essentially anything that looks manipulable by the user - and select the "Events" tab. Here, you'll find the various actions attributed to this form element (ie: beforeUpdate, onClick, etc). If you want a confirmation for the update first, follow this process:
· select your command button, open the properties dialog.
· select the "other" tab, and name the button according to conventions (cmd<WhatItDoes>).
· select the event tab, find "onClick" (when you focus on this element, a small button with an ellipsis will appear to the right - you can use this or the drop down to select "[Event Procedure]" - which you will use to open the code window.
· look up in Access Help how to use Y/N message boxes as a starting point for data operations - they're great for deciding simple cases (if yes, do this; if no, don't do this).
Then (provided you want the form to close regardless of what they click), in the end of each selection's code you'll put a line with a command ("DoCmd." element) that tells that particular form to close itself.
Once you start learning the VBA code this way, you'll be able to intuitively answer a lot of these questions on your own. I started doing that, and it's really helped me a great deal - Pat will tell you, I was really at a loss there in March/April. ^_^
Just my two bits on how to be successful with Access. The forums are great, but there are a LOT of duplicate questions floating around. You're not dumb, for the record - my boss is dumb. At least you understand the value of Access and the value of well placed questions. ^_^
The other thing that really helped me was the deprecated Object Model for Access. Hey, Pat - do you have a link to that somewhere? I can't find one, and the one I have isn't on my office machine.
Cheers!
- Z
Me think me like to build! GRUNT! Now I regret not taking a few programming courses....but, I think I will over the next few years....will complement my support and avionics experience. 