Combo Box not in Source Control in order to bind

[JHG]

I have 11 Fields in the Control Source Box. 5 of those is Combo Boxes. Only 4 of the 5 Combo Boxes show in the Control Source Box to bind.


Thank You.

[CJ_London]

not clear what you question is - If it is 'how do you bind a control to a field?' then you put the field name in the control controsource property

[JHG]

Ok I will try and explain better.

As you can see in the image, all the combo boxes are bound except one "Hanging". I am unable to bind it, because it does not show or reflect in the box when I click on the "Source Control" of this item.

You will also notice that the table for "Hanging" is available as well. "Hanging" does not show in it's "Source Control". Therefore it is impossible to bind it unlless there is another possible method.

[davegri]

If the fieldname does not appear in the control's Control Source, it's because the field is not included in the form's recordsource.

[June7]

Field must be in form's RecordSource for it to be available for binding to a control.

What table is the form bound to - StockInfoT? What field should HangingT primary key be saved into as foreign key?

Have you reviewed article about inventory control referenced in your other thread? http://allenbrowne.com/AppInventory.html

[moke123]

You should also note that Size and Type are reserved words and may cause you some unexpected errors.

http://allenbrowne.com/AppIssueBadWord.html#S

[CJ_London]

just wondering, since you appear to be wanting to bind to a table whether you mean the rowsource to the combo?

[JHG]

I am so stupid. All of you are correct. I never put the table name in the main table which is stock info.


I will correct it and see if it works

[JHG]

Thanx everybody it is working now. I do not know how I missed it. Lack of Knowledge and experience I guess.

[moke123]

You should really consider changing the field names "Type" and "Size". They are reserved words.
Another thing to consider is the use of attachment fields. They are rarely a good thing and tend to bloat a database.

[JHG]

Yes I agree with you. If it is reserved words there could probably be a problem with other languages like VB or Python or so. I will change them to something else.
It is at the moment easy to use the attachment field, because it is easier. If I have access under control, I will probably find another way to do this.

[moke123]

It is at the moment easy to use the attachment field, because it is easier.

I dont use them because I find them harder to code for.
Much easier to store the path to a photo as text.

[JHG]

I am actually a Layman and a dummy. I am learning Access from youtube videos. They have not taught me to do that yet. I tried to look myself now, but could not see how.

[June7]

Embedding objects in table uses up Access 2GB file size limit faster. This might never be an issue for this db but certainly something to consider.

Yes, Attachment field has its own 'wizard' dialog for adding files which makes it very easy and tempting to utilize. Storing just file path requires VBA executing Windows File Dialog to navigate and select file - unless you want to allow user to type or copy/paste file path into text field which is certainly prone to errors.

[moke123]

There are several other methods you could use in addition to Junes suggestion of filedialog. A lot depends on what your doing and how your doing it.
If you name your attachments like GreenArrow.jpg and FirstAid.jpg or use the item number E2.jpg and E23.jpg, you can store them all in one folder, name it ProductPictures and then concatenate the path when needed with something like CurrentProject.Path & "\ProductPictures" & Me.ItemName & ".jpg"