If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Other > Access Database Design

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-07-04, 18:12
ulysses ulysses is offline
Registered User
 
Join Date: Mar 2004
Location: Toronto
Posts: 1
Wink Access Database Design

I have been requested to make an database using Access which will store a certain set of records.

Now, I have no Idea on how I should do the design of the database tables.

Daily there will be aprox. 150 records added to the database and the primary key will be a UserID.

Now, is it better to just make one LARGE Database with all these records(and trust me it will get really large) or do i create Weekly databases? So after each week, some how I have to figure out a trigger to create a new database the same as the last weeks, but empty.

Any suggestions on what would be the best course of action?


Users get added to the database (seperate table) daily.

Please, any suggestion would help greatly.

Ulysses
Reply With Quote
  #2 (permalink)  
Old 03-08-04, 11:28
JODonnell JODonnell is offline
Registered User
 
Join Date: Feb 2004
Location: Pittsburgh, PA
Posts: 41
Re: Access Database Design

Hi,

My experience with tabes broken out by periods of time has been less than great. I would reccomend putting all the related data into one table and using indexes if it starts to take too long to query.

Don't forget about the 2 Gig file limit in access though.

Good luck,

John
Quote:
Originally posted by ulysses
I have been requested to make an database using Access which will store a certain set of records.

Now, I have no Idea on how I should do the design of the database tables.

Daily there will be aprox. 150 records added to the database and the primary key will be a UserID.

Now, is it better to just make one LARGE Database with all these records(and trust me it will get really large) or do i create Weekly databases? So after each week, some how I have to figure out a trigger to create a new database the same as the last weeks, but empty.

Any suggestions on what would be the best course of action?


Users get added to the database (seperate table) daily.

Please, any suggestion would help greatly.

Ulysses
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On