Listbox displaying only numbers

Alright Micron, I will defer to you and refrain from distracting about the list box. Good idea.
 
Have a look at this sample database.


I will sir. Thank you.
 
How about I just throw everything out here given that I suspect it will all be news. Start with the normalization. If it doesn't sink in, find your own links that 'speak' to you. If you do not grasp normalization you will always struggle. I'm not saying you have to be a wizard at it, just understand enough to succeed.
Normalization is paramount. Diagramming maybe not so much for some people.

Normalization Parts I, II, III, IV, and V (make sure to follow the links - they're not obvious)
and/or

Entity-Relationship Diagramming: Part I, II, III and IV

How do I Create an Application in Microsoft Access?

Naming conventions
- http://access.mvps.org/access/general/gen0012.htm
- https://www.access-programmers.co.uk/forums/showthread.php?t=225837

What not to use in names - http://allenbrowne.com/AppIssueBadWord.html

About Auto Numbers
- http://www.utteraccess.com/wiki/Autonumbers
- http://access.mvps.org/access/general/gen0025.htm

The evils of lookup fields - http://access.mvps.org/access/lookupfields.htm
Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp
About calculated table fields - http://allenbrowne.com/casu-14.html
About Multi Value Fields - http://www.mendipdatasystems.co.uk/multivalued-fields/4594468763
 
How about I just throw everything out here given that I suspect it will all be news. Start with the normalization. If it doesn't sink in, find your own links that 'speak' to you. If you do not grasp normalization you will always struggle. I'm not saying you have to be a wizard at it, just understand enough to succeed.
Normalization is paramount. Diagramming maybe not so much for some people.

Normalization Parts I, II, III, IV, and V (make sure to follow the links - they're not obvious)
and/or

Entity-Relationship Diagramming: Part I, II, III and IV

How do I Create an Application in Microsoft Access?

Naming conventions
- http://access.mvps.org/access/general/gen0012.htm
- https://www.access-programmers.co.uk/forums/showthread.php?t=225837

What not to use in names - http://allenbrowne.com/AppIssueBadWord.html

About Auto Numbers
- http://www.utteraccess.com/wiki/Autonumbers
- http://access.mvps.org/access/general/gen0025.htm

The evils of lookup fields - http://access.mvps.org/access/lookupfields.htm
Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp
About calculated table fields - http://allenbrowne.com/casu-14.html
About Multi Value Fields - http://www.mendipdatasystems.co.uk/multivalued-fields/4594468763


Thank you
 
You make a lot of errors to define your relations.
  • first of all: a primary key refers to a foreign key from the first table to the second one. You can't set a relation between two tables on the two primary keys
  • you have to set a relation one to many between both tables: from table one primary key (autonumber) to table two (number field) (with the same name as the primary key of table one.
  • then you have to create a query to fill the listbox
    Asset.png
Code:
    sqlListOne = "SELECT Asset, SerialNo " & _
        "FROM AssetList INNER JOIN AssetInfo ON AssetList.IDAssetList = AssetInfo.IDAssetList;"
  • then you have to activate the listbox
Code:
    With Me.lstOne
        .RowSource = sqlListOne
        .ColumnCount = 2
        .ColumnWidths = "3cm;2cm"
    End With

If this is what you want to see. Or else: create two form a parent and a child form.
 

Users who are viewing this thread

Back
Top Bottom