| |
|
If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.
|
 |

03-19-06, 13:34
|
|
Purveyor of Discontent
|
|
Join Date: Mar 2003
Location: The Bottom of The Barrel
Posts: 6,075
|
|
|
MS Access FAQ (Read Me First - NO SERIOUSLY)
YAY, A FAQ!
Hey, this FAQ is outright anemic, what gives?
I know, I know. This FAQ is just getting off the ground and doesn't have much useful content yet. If you have a suggestion for a FAQ to be written or [Hallelujah] are willing to write one yourself[/Hallelujah], please, PLEASE PM me and I'll post the topic here/post your faq.
Also, I'm still open to ideas about the format of the individual FAQ's. If you have an opinion on the matter, let it be heard here. We don't bite... hard... unless you ask... then it costs money.
Also Also, If you happen to peruse the thread while it's not locked, please do not post. I am trying to restrict this thread to only FAQ's, discussion about the FAQ's would be better placed elsewhere... like here, for instance
General Topics
Requested FAQ Topics: - Cascading ComboBoxes
- *** Your suggestion here ***
|
Last edited by Teddy; 04-17-06 at 12:24.
|

03-19-06, 13:39
|
|
Purveyor of Discontent
|
|
Join Date: Mar 2003
Location: The Bottom of The Barrel
Posts: 6,075
|
|
What's a FAQ?
FAQ:Frequently Asked Questions.
A FAQ is a list of common questions with their answers, maintained by most special interest groups on the Internet as a way of lowering the frequency of basic technical questions.
The MS Access FAQ contains the most commonly asked questions (and their solutions) seen over time in the MS Access forum.
|
Last edited by Teddy; 04-17-06 at 12:23.
|

03-19-06, 14:05
|
|
Purveyor of Discontent
|
|
Join Date: Mar 2003
Location: The Bottom of The Barrel
Posts: 6,075
|
|
What is DBForums?
DBForums is a free forum supported by and for our members. Our active members are here because they enjoy helping folks out (and occassionally need a lifeline  ).
What ISN'T DBForums?
DBForums may be helpful in a variety of situations, but it is not the one-stop shop for every situation. Here are a few things the MS Access fourm is not- Paid Tech Support:
We are not a paid tech support forum. Please keep this in mind when evaluationg responses to your questions. It is unrealistic to hold an expectation of service above and beyond that of a forum comprised of volunteer members who share their knowledge, experience and solutions just because they like to help. If you expect or demand solutions from our members, you will be unlikely to receive any useful information. If your expectations are flagarantly obnoxious/unrealistic, expect your post to be moderated.
- A Substitute for Talking With Your Professor/Classmates:
Homework questions are ok. Everybody has to start somewhere, and school isn't all that bad of a place to begin. If you are stuck with a specific problem or concept, feel free to post and we will assist to the best of our ability. However, attempting to coerce members into completing your homework for you is definately NOT ok. If you do so, your post will be moderated. If you continue to do so, you will be banned.
- Classified Section:
Job offers or positions should be posted in the Job Opportunities section. If you find yourself in a position where you MUST demand an immediate solution, you will probably have to pay for it. The Job Opportunities forum isn't a bad place to ask. Please do not post open positions or contract opportunities in the Access forum. If you do so, your post will be moderated. If you continue to do so, you will be banned.
|
Last edited by Teddy; 04-17-06 at 12:23.
|

03-19-06, 14:24
|
|
Purveyor of Discontent
|
|
Join Date: Mar 2003
Location: The Bottom of The Barrel
Posts: 6,075
|
|
How Do I Ask A Question?
You may notice that some folks get their questions answered almost immediately while others will languish for days before receiving their first reply. Contrary to popular belief, this rarely has anything to do with us playing favorites (sometimes it does, but that's only if the poster is exceptionally awesome). In general, the reason one question gets a plethora of support while another gets squat is because of how the question was asked.
Some of our members are quite skilled in a variety of disciplines, some are outright experts, none are cairvoyant. When posting your question, please include: - POST YOUR ACTUAL QUESTION IN THE THREAD TITLE. The fact that you are posting here in the first place is a good indicator that you "NEED HELP PLZ!11!". You are more likely to receive timely assistance if there is something meaningful in your thread title that will allow someone scanning the forums to identify your post as an area of their expertise.
- What version of Access you're using
- The business logic or problem you are trying to solve with your application
- The SPECIFIC behavior or lack thereof that describes your problem
- If you're posting regarding an error, please, post the error. C'mon, seriously folks.
- Post your current solution, what it's doing that you don't like AND an example of your desired results
For general SQL/table design/query issues, this would include a full description of the tables involved; Sample data; and sample result records.
Also, we do not know anything about your project or application unless you explicitly tell us about it. That means a question such as, "The client button doesn't populate the third insurance claim selector with the code!!!" will go unanswered. We don't know what you're talking about, sorry.
In short, give us half a chance at actually being able to answer your question. Make it as easy as possible, and you're FAR more likely to get a response.
When you have arrived at a solution to your problem, please report back to the thread to let us know what did the trick. I know it cuts into your time a bit and isn't necessary once you solved your issue, but gee golly it gives us the warm fuzzies and helps out the next poor schmoe who comes along with the same question. As a bonus, we'll take a shine to ya'
|
Last edited by Teddy; 12-21-06 at 16:50.
|

04-17-06, 12:18
|
|
Purveyor of Discontent
|
|
Join Date: Mar 2003
Location: The Bottom of The Barrel
Posts: 6,075
|
|
Get Selected Values From A Listbox
For the purposes of this FAQ, we will assume a form with two controls:
lstMyListBox - Listbox control
btnDemo - Command Button
Listboxes offer three "multi-select" modes to control how a user may interact with the listbox. The first mode, "none", only allows the user to select one item at a time. To evaluate the current selection with lstMyListBox's multi-select property set to "none", we could use the following code:
Debug.Print Me.lstMyList.Column(0, lstMyList.ListIndex)
If lstMyListBox is set to either "simple" or "extended" multiselect, we have to approach the issue a little differently. Listboxes have a collection called "ItemsSelected". This collection contains all of the currently selected rows. When we iterate through the ItemsSelected collection, we will receive the index of the selected items. Here is an example of how that might look:
Code:
Private Sub btnDemo_Click()
Dim varItem As Variant
For Each varItem In Me.lstMyList.ItemsSelected
Debug.Print lstMyList.Column(0, varItem)
Next varItem
End Sub
Dim varItem As Variant
This line creates a variable that will hold each index as we iterate through the ItemsSelected property.
For Each varItem In Me.lstMyList.ItemsSelected
This line tells access to go through the ItemsSelected property one-at-a-time and place the contents into varItem.
Debug.Print lstMyList.Column(0, varItem)
This prints the contents of the selected row to the intermediate window
Next varItem
Get the next selected row.
|
|

07-19-07, 17:36
|
|
Moderator
|
|
Join Date: Dec 2004
Location: Madison, WI
Posts: 3,925
|
|
|
__________________
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)
|
Last edited by pkstormy; 07-19-07 at 17:55.
|

07-20-07, 13:10
|
|
Moderator
|
|
Join Date: Dec 2004
Location: Madison, WI
Posts: 3,925
|
|
2 Versions of MSAccess problems, missing code:
If you have 2 versions of MSAccess or get a wierd error when opening your form, report or mdoule and find that some of your code is missing, try looking at these posts:
Access Ate my Code
http://www.dbforums.com/archive/inde...t-1212300.html
__________________
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)
|
|

11-19-07, 12:28
|
|
Super Moderator
|
|
Join Date: Jun 2004
Location: Arizona, USA
Posts: 1,797
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|