|
| 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. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#11
April 2nd, 2007, 10:28 AM
posted to microsoft.public.access.forms
|
|||
|
|||
*#$&@%^ combo box in a form
It wasn't a combo box.
Now I found the combo box control & inserted it but it will only display the primary key, not the text associated with the primary key. How do I fix that? You guys are so patient - thanks. -- Thanks for your time! "Rick Brandt" wrote: NC_Sue wrote: As I said in last post, "Row source" does not appear anywhere, even under the ALL tab of the property box. It simply ain't there. Then either... You do not have the control in question selected. or The control in question is not a ComboBox. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com 
|
|
#12
April 2nd, 2007, 10:46 AM
posted to microsoft.public.access.forms
|
|||
|
|||
|
*#$&@%^ combo box in a form
Have you tried what I suggested in first post?
-- Good Luck BS"D "NC_Sue" wrote: It wasn't a combo box. Now I found the combo box control & inserted it but it will only display the primary key, not the text associated with the primary key. How do I fix that? You guys are so patient - thanks. -- Thanks for your time! "Rick Brandt" wrote: NC_Sue wrote: As I said in last post, "Row source" does not appear anywhere, even under the ALL tab of the property box. It simply ain't there. Then either... You do not have the control in question selected. or The control in question is not a ComboBox. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com
|
|
#13
April 2nd, 2007, 07:44 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
*#$&@%^ combo box in a form
"NC_Sue" wrote: I have a dropdown box in the table Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Before you click on the Dropdown button in the form design view make sure the Wizard button is on (looks like a magic wand). This will walk you through setting up the combo box. Once the wizard is finished go back to the properties for that object and look at them. See how the information you gave the wizard was applied. This is how I learned to do them on my own - use the Wizard first, see what it did then try it myself. Lauri
|
|
#14
April 4th, 2007, 09:32 AM
posted to microsoft.public.access.forms
|
|||
|
|||
|
*#$&@%^ combo box in a form
Lauri
Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Not quite True. Tables can be used to store data as lookup data for inserting into other tables ie say for Postcodes for a persons address..using a combo box here would list the postcodes one could select and this can then be used to automatically set Suburb etc after selecting the postcode.... Also a feature of Access is in setting a particular field in the table design to a combo box and establishing its lookup query and columns in the actual table. This will then mean that when a user selects a field from the field list in the form design and drops it onto the form, the field will automatically be a dropdown combo box with all its lookup and column details set. This type of feature is what makes Access such a powerful rapid development environment. the reest is there.... Agree with using the wizard for novices...a great way to learn.... my 2 bobs worth!  cheers jeff "LauriS" wrote in message ... "NC_Sue" wrote: I have a dropdown box in the table Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Before you click on the Dropdown button in the form design view make sure the Wizard button is on (looks like a magic wand). This will walk you through setting up the combo box. Once the wizard is finished go back to the properties for that object and look at them. See how the information you gave the wizard was applied. This is how I learned to do them on my own - use the Wizard first, see what it did then try it myself. Lauri
|
|
#15
April 4th, 2007, 12:30 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
*#$&@%^ combo box in a form
jeff wrote:
Lauri Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Not quite True. Tables can be used to store data as lookup data for inserting into other tables ie say for Postcodes for a persons address..using a combo box here would list the postcodes one could select and this can then be used to automatically set Suburb etc after selecting the postcode.... Lauri was not saying that tables *could not* be used this way, but rather that they *should not* be. At least not in anything more serious than a CD collection table. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com
|
|
#16
April 4th, 2007, 01:38 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
*#$&@%^ combo box in a form
Care to give another 2 bobs or so?
I tried Lauri's suggestions & now when I enter a contact type for one person, EVERYONE's contact type changes to match that particular person. Why come??? -- Thanks for your time! "jeff" wrote: Lauri Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Not quite True. Tables can be used to store data as lookup data for inserting into other tables ie say for Postcodes for a persons address..using a combo box here would list the postcodes one could select and this can then be used to automatically set Suburb etc after selecting the postcode.... Also a feature of Access is in setting a particular field in the table design to a combo box and establishing its lookup query and columns in the actual table. This will then mean that when a user selects a field from the field list in the form design and drops it onto the form, the field will automatically be a dropdown combo box with all its lookup and column details set. This type of feature is what makes Access such a powerful rapid development environment. the reest is there.... Agree with using the wizard for novices...a great way to learn.... my 2 bobs worth! cheers jeff "LauriS" wrote in message ... "NC_Sue" wrote: I have a dropdown box in the table Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Before you click on the Dropdown button in the form design view make sure the Wizard button is on (looks like a magic wand). This will walk you through setting up the combo box. Once the wizard is finished go back to the properties for that object and look at them. See how the information you gave the wizard was applied. This is how I learned to do them on my own - use the Wizard first, see what it did then try it myself. Lauri
|
|
#17
April 4th, 2007, 01:42 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
*#$&@%^ combo box in a form
Can you tell me the best way to proceed, then? At this point I seem unable to
get the dropdown box in my form to function as I want it to. Either EVERYONE's contact type gets changed to the same value when I change this field for one individual or I can only get the numeric key to display, not the text. Do I need to change my tables? My forms? My relationships? -- Thanks for your time! "Rick Brandt" wrote: jeff wrote: Lauri Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Not quite True. Tables can be used to store data as lookup data for inserting into other tables ie say for Postcodes for a persons address..using a combo box here would list the postcodes one could select and this can then be used to automatically set Suburb etc after selecting the postcode.... Lauri was not saying that tables *could not* be used this way, but rather that they *should not* be. At least not in anything more serious than a CD collection table. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com
|
|
#18
April 4th, 2007, 01:54 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
*#$&@%^ combo box in a form
That's usually indicative that your combo box isn't bound to a field in your
form's underlying RecordSource. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "NC_Sue" wrote in message ... Care to give another 2 bobs or so? I tried Lauri's suggestions & now when I enter a contact type for one person, EVERYONE's contact type changes to match that particular person. Why come??? -- Thanks for your time! "jeff" wrote: Lauri Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Not quite True. Tables can be used to store data as lookup data for inserting into other tables ie say for Postcodes for a persons address..using a combo box here would list the postcodes one could select and this can then be used to automatically set Suburb etc after selecting the postcode.... Also a feature of Access is in setting a particular field in the table design to a combo box and establishing its lookup query and columns in the actual table. This will then mean that when a user selects a field from the field list in the form design and drops it onto the form, the field will automatically be a dropdown combo box with all its lookup and column details set. This type of feature is what makes Access such a powerful rapid development environment. the reest is there.... Agree with using the wizard for novices...a great way to learn.... my 2 bobs worth! cheers jeff "LauriS" wrote in message ... "NC_Sue" wrote: I have a dropdown box in the table Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Before you click on the Dropdown button in the form design view make sure the Wizard button is on (looks like a magic wand). This will walk you through setting up the combo box. Once the wizard is finished go back to the properties for that object and look at them. See how the information you gave the wizard was applied. This is how I learned to do them on my own - use the Wizard first, see what it did then try it myself. Lauri
|
|
#19
April 4th, 2007, 01:58 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
*#$&@%^ combo box in a form
NC_Sue wrote:
Can you tell me the best way to proceed, then? At this point I seem unable to get the dropdown box in my form to function as I want it to. Either EVERYONE's contact type gets changed to the same value when I change this field for one individual That means you didn't bind the ComboBox to a field in your table. or I can only get the numeric key to display, not the text. Do I need to change my tables? My forms? My relationships? You need a two column ComboBox. The first column is hidden and is the bound column holding the ID and hte second visible column show the text. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com
|
|
#20
April 4th, 2007, 02:02 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
*#$&@%^ combo box in a form
I think I'm chasing my tail here.
I simply cannot find "record source" anywhere when I call up the property box for that field... not under "data source" tab, not under "all" tab. I must be a doofus or something. -- Thanks for your time! "Douglas J. Steele" wrote: That's usually indicative that your combo box isn't bound to a field in your form's underlying RecordSource. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "NC_Sue" wrote in message ... Care to give another 2 bobs or so? I tried Lauri's suggestions & now when I enter a contact type for one person, EVERYONE's contact type changes to match that particular person. Why come??? -- Thanks for your time! "jeff" wrote: Lauri Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Not quite True. Tables can be used to store data as lookup data for inserting into other tables ie say for Postcodes for a persons address..using a combo box here would list the postcodes one could select and this can then be used to automatically set Suburb etc after selecting the postcode.... Also a feature of Access is in setting a particular field in the table design to a combo box and establishing its lookup query and columns in the actual table. This will then mean that when a user selects a field from the field list in the form design and drops it onto the form, the field will automatically be a dropdown combo box with all its lookup and column details set. This type of feature is what makes Access such a powerful rapid development environment. the reest is there.... Agree with using the wizard for novices...a great way to learn.... my 2 bobs worth! cheers jeff "LauriS" wrote in message ... "NC_Sue" wrote: I have a dropdown box in the table Problem #1. Tables are for storing data - not selecting it. Dropdowns belong only in the forms - not in the tables. Before you click on the Dropdown button in the form design view make sure the Wizard button is on (looks like a magic wand). This will walk you through setting up the combo box. Once the wizard is finished go back to the properties for that object and look at them. See how the information you gave the wizard was applied. This is how I learned to do them on my own - use the Wizard first, see what it did then try it myself. Lauri
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
