Why is Income Type not a Table
If you have a new IT does that mean you are adding a new Field?

Yea I would just make income type a table. Then you only need to have your autonumber, IncomeAmount and IncomeType, not 50 fields.

Relationships

The income types as fields essentially mirror the fields from my source i.e. tax software. I'll export tax client tax return data into excel, and then into the Access Database fields and all. Thus the Access database is essentially an exact replica of the excel worksheet i.e 60 columns of tax return data (including the 50 income columns), and 150 rows of clients. The income types never change

So I guess the format i.e income types as fields is out of convenience.

The Access reports are solely for my avoiding having to format 150 clients separate excel tax worksheets that I can present to clients.

Adam,

Thank you for the Link. I'll take a look.

Thankfully Access in its current form will be a great benefit for my client projections due in two weeks. My plan for 2022 is to get Access to do do all the heavy lifting by my creating queries by client. This year I will have to export the Access reports back to excel so that I can manually add projection formatting and calculations beyond my current Access expertise.

Many thanks all

You could also check out the extended cut of Loan Payments about crosstab queries, if you set it up as Alex and I suggested, you could use a crosstab to still get the information to appear like an excel sheet with columns having their own "Income Type"

You would need a membership to view that though, although I would recommend you get that anyways if your goal is to be using Access longterm, theres SO much information available in them, so many videos, for like 20 cents a day. It's amazing value.

Adam

Thank you. Membership is a definite. Looking to take full advantage of this terrific Pegram

err Program...

Hi Michael. It's not easy to hide fields on FORMS and have the following lines "squish up" so as not to lose space, however you can do it on reports with the Can Shrink property. However, like the guys already suggested, I wouldn't use 50 separate fields in your table. I'd make it a related second table.