Issue with Calculating Fields in SharePoint (Projected Fields?)

[Heatshiver]

I am creating a DB for SharePoint in Access but it has more than 255 fields, so I am forced to use separate tables.

The database consists mainly of input fields and calculated fields that retrieve its values from the input fields. I wanted to separate the calculated fields from the input fields and have them in their own respective fields.

My problem is that I can create a LookUp field for the calculated fields to retrieve the values from the input table, but it seems to only see the value of the field (when creating an expression) that was selected for the LookUp field name (although I chose all the fields I needed to create the calculation).

I could create one LookUp field per input field value needed, but this would be long and tedious.

Is there a simple way I can get all the input values to show in the expressions of the calculated fields? I read up on Projected Fields, but can I create this in Access (or only in the SharePoint interface)?

 

[RossWindows]

As a general rule, if you have anywhere close to 255 fields in a single table, you're database needs to be normalized.

When it comes to storing data in a database format, you only store the raw values and when it comes to displaying a calculated value you can do that in a query on the fly. There are exceptions to every rule though so without looking at your data I can't say for sure.