Subdatasheets, Multiple Linked tables

[fktx]

I will admit I new to designing databases, but I am not a computer novice by
any means. I am trying to design a simple database about ocean currents at
various locations throughout the Gulf. Initially, I was going to use 3 tables
within a single database to store the data, but I would have easily surpassed
the 2GB barrier after adding just a couple of locations. Therefore, I am
forced to put the data for each station into its own database, and then link
all the stations through a Master database. The primary key in the Master
database is a unique StationNumber that is also appended to the data in each
of the station databases.

My problem arises when I try to view subdatasheets within the Master
database. It seems Access allows just 1 linked table to supply ALL the data
for viewing in the subdatasheets. However, I would like to be able to view
subdatasheets for more than one linked table. So, I guess my question is how
can I link multiple databases to one, and still be able to view the
subdatasheets for each linked table?

F.K.

 

[John W. Vinson]

My problem arises when I try to view subdatasheets within the Master
database. It seems Access allows just 1 linked table to supply ALL the data
for viewing in the subdatasheets. However, I would like to be able to view
subdatasheets for more than one linked table. So, I guess my question is how
can I link multiple databases to one, and still be able to view the
subdatasheets for each linked table?

Subdatasheets - and table datasheets in general - are a VERY limited tool. In
addition, if your tables are at all large (and yours are evidently huge!) they
are extreme drags on performance.

Instead, use Forms as tools to display data. A Form can have multiple Subforms
to display data from related tables.

Given the scale of your project, though, I'd really, really suggest moving
your data to SQL/Server. Pushing the 2 GByte limit can cause all sorts of
problems in Access, and you'll have real problems with query optimization at
this size scale; SQL can handle terabyte datasets with aplomb given proper
database design. In addition you can use Access (*with* Forms and Subforms,
not subdatasheets) as a user interface.

 

[Fred]

While I CAN imagine three dimensional data for points in a large body
burying Access (such has even buried supercomputers), my gut feel from your
inquiry is that you haven't really entered that much data yet (????)