Re: Separate user inputs into a single table?

That you are having this issue is, I think, related to the answer I gave to your other question about normalization.

If you think vertically, rather than horizontally, then the users are not working on the same record and there is no issue.

Daniel Morgan

AEG wrote:

> I have a table with a primary key of 4 columns. It has a set of columns
> (A1, A2, A3, etc.)
> and a set of columns (B1, B2, B3, etc.). Each column is to contain
> identical sets of data
> ie, A1 = B1, A2 = B2, A3 = B3, etc. I also have 2 columns to keep track of
> different
> users A_USER, B_USER. The idea is to have A_USER enter data for the A
> columns, and the B_USER enter data for the B columns, and then verify that
> the columns entered by each user match for each record entered. The main
> requirements are:
>
> 1. User A is not the same as user B, and
> 2. Users are not locked out of records when another user is accessing the
> database table from
> a data entry form.
>
> So basically, given the main requirements above, my question is:
> Does the above table setup make sense? And do you forsee any problems with
> accessing
> records in the table?
>
> Basically, the above appears to make sense, but others have suggested a
> design which puts
> columns A1, A2, A3, etc. and B1, B2, B3, etc. into separate tables. Code is
> then used to
> compare users and data in the columns in the 2 tables, etc. To me, this
> seems
> unnecessarily complex. Am I missing something here?
>
> Thanks in advance,
>
> AEG
Received on Wed Feb 06 2002 - 10:45:27 CST