Massive Database

[Mary Bronson]

I am designing a database for work. This is a massive
database containing 6 different Tables. All tables
require certain information.

After all the data is entered, I am required to be able
to export it in a Fixed Field and all the formats
appended together.

Also on one of the fields, I need to make a Valadation
rule not allowing certain states to be typed.

Any help will be appreciated.

 

[John Vinson]

I am designing a database for work. This is a massive
database containing 6 different Tables. All tables
require certain information.

What's "massive"? How many records in the largest table? (I'd call
over ten million records "massive", over a million "large"). Access
databases are limited to 2 GByte (including all the tables, forms,
reports, and overhead) - are you pushing this limit?

Six tables is rather small as database structure goes.

After all the data is entered, I am required to be able
to export it in a Fixed Field and all the formats
appended together.

You'll have to explain what you mean. I'd presume that you could
create a Query joining the six tables and export from that, if the
resulting query has fewer than the 255-field limit enforced by Access;
but "all the formats" has no meaning to me.

Also on one of the fields, I need to make a Valadation
rule not allowing certain states to be typed.

Access knows nothing about "states" of course. If you mean states of
the United States, I'd suggest that the simplest way to deal with this
constraint is to create a States table with the two-letter state codes
of the *allowed* states, and create a Relationship between this field
and this table, with relational integrity enforced. This will keep the
user from entering any other state code, and have the added advantage
that you can use a Combo Box based on the states table so the user can
pick from a list rather than having to remember whether Minnesota is
MI, MN, ME or MS.