One database or more

[Ron A.]

I need to create a database to track convention attendees, their lodging
arangements, Hotel info, if attendees need transportation to and from the
airport and convention and pickup/dropoff times, convention volunteers and
their assignments.

Would it be logical to do it all in one database or should I make 2. One for
the convention attendees info and lodging and 1 for the transportation needs
of the attendees? What would be the best solution?

 

[boblarson]

If it is all for the same thing, I see no benefit to doing it up as separate.
I would do it all together.

--
Bob Larson
Access MVP
Access World Forums Administrator
Utter Access VIP

Tutorials at http://www.btabdevelopment.com

__________________________________

 

[Douglas J. Steele]

Are you talking separate MDB (or ACCDB) files, or are you misusing the term
databases, and really mean tables? If the former, I definitely agree with
Bob. If the latter, yes, you'll need multiple tables to model it correctly.

 

[Ron A.]

I am talking about seperate ACCDB files. It am not sure if tracking such
different types of data (convention attendee contact info and limousine type
services for the convention) in one database is the way to go. I just want to
start out with a solid foundation to prevent issues when the database will be
put to use.
--
Aloha,
Ron A.

Are you talking separate MDB (or ACCDB) files, or are you misusing the term
databases, and really mean tables? If the former, I definitely agree with
Bob. If the latter, yes, you'll need multiple tables to model it correctly.

 

[John W. Vinson]

I am talking about seperate ACCDB files. It am not sure if tracking such
different types of data (convention attendee contact info and limousine type
services for the convention) in one database is the way to go. I just want to
start out with a solid foundation to prevent issues when the database will be
put to use.

One accdb database can contain many, many tables - upwards of 1000 if I recall
aright. Since attendee information is logicallly related to how those
attendees are transported, then I would absolutely recommend using on database
with multiple tables (e.g. tables for attendee information, convention
information, locales, transportation providers, trips, and doubtless others).