By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,952 Members | 1,722 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,952 IT Pros & Developers. It's quick & easy.

Table design suggestions please...?

P: n/a
Hi,

I'd like some suggestions on a db design.

The data source is pretty simple. I'll be importing from an excel
spreadsheet. There could be 4 to 12 rows, and there will always be
the same amount of columns as rows.

row headers and column headers are just numbers, and the actual data
again is just numbers.

There will be about 30 "pages" for each spreadsheet, ie, the number of
times I'll import the same spreadsheet will be 30, as it's dynamically
updated with current numbers.

example:

ID 1 2 3 4 5
1 x 45 23 12 54
2 12 x 34 23 12
3 14 34 x 12 54
4 23 43 65 x 87
5 87 23 23 32 x

I was thinking of having a table for rows/column number (ID), and a
table for each "page" (up to 30). Then a table that links each ID to
the other ID. That design works, but it's not the most efficient,
cause it doesn't seem to be normalized the best.

Anybody have a more elegent way of storing layered tables?

Thanks,
Bodi
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Bodi wrote:
Hi,

I'd like some suggestions on a db design.

The data source is pretty simple. I'll be importing from an excel
spreadsheet. There could be 4 to 12 rows, and there will always be
the same amount of columns as rows.

row headers and column headers are just numbers, and the actual data
again is just numbers.

There will be about 30 "pages" for each spreadsheet, ie, the number of
times I'll import the same spreadsheet will be 30, as it's dynamically
updated with current numbers.

example:

ID 1 2 3 4 5
1 x 45 23 12 54
2 12 x 34 23 12
3 14 34 x 12 54
4 23 43 65 x 87
5 87 23 23 32 x

I was thinking of having a table for rows/column number (ID), and a
table for each "page" (up to 30). Then a table that links each ID to
the other ID. That design works, but it's not the most efficient,
cause it doesn't seem to be normalized the best.

Anybody have a more elegent way of storing layered tables?

Thanks,
Bodi


YOu can link the spreadsheet within Access and it becomes a table
withing Access. You can then update the data either in Excel or Access.
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.