Listbox displaying only numbers (1 Viewer)

rayape

Registered User.
Local time
Yesterday, 21:29
Joined
Dec 12, 2012
Messages
56
Well, that's different than what you first posted you saw. :unsure:

Originally, I only had Columns 2 and 3. I had omitted the first column. Since your post, I wanted to make sure the ColumnCount property was set correct. The updated image shows all 3 columns. That's it.

Thank you
 

Micron

AWF VIP
Local time
Today, 03:29
Joined
Oct 20, 2018
Messages
3,478
I suggest you forget about the listbox issue. You have bigger problems with tables design, which when fixed, will likely make your list box unusable again.
 

rayape

Registered User.
Local time
Yesterday, 21:29
Joined
Dec 12, 2012
Messages
56
I suggest you forget about the listbox issue. You have bigger problems with tables design, which when fixed, will likely make your list box unusable again.

I am learning about it through all you learned folks. Please give me some pointers to fix the whole thing.
Thank you all.
 

Isaac

Lifelong Learner
Local time
Today, 00:29
Joined
Mar 14, 2017
Messages
8,777
Alright Micron, I will defer to you and refrain from distracting about the list box. Good idea.
 

Uncle Gizmo

Nifty Access Guy
Staff member
Local time
Today, 08:29
Joined
Jul 9, 2003
Messages
16,282
Please give me some pointers to fix the whole thing.

Have a look at this sample database.

 

rayape

Registered User.
Local time
Yesterday, 21:29
Joined
Dec 12, 2012
Messages
56
Have a look at this sample database.


I will sir. Thank you.
 

Micron

AWF VIP
Local time
Today, 03:29
Joined
Oct 20, 2018
Messages
3,478
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
 

rayape

Registered User.
Local time
Yesterday, 21:29
Joined
Dec 12, 2012
Messages
56
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
 

so10070

Registered User.
Local time
Today, 09:29
Joined
Aug 18, 2016
Messages
51
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.
 

Uncle Gizmo

Nifty Access Guy
Staff member
Local time
Today, 08:29
Joined
Jul 9, 2003
Messages
16,282
Or else: create two form a parent and a child form

Sample already provided:-

 

Users who are viewing this thread

Top Bottom