Club Member Database

[butterbescotch]

It would really mean a lot of your help. This is just a simple database, however, I really forgot how to build one.


The image says it all

[June7]

A: Avoid spaces and special characters/punctuation (underscore is exception); some like to use a prefix for object names (tbl, qry, frm, rpt).

B: Will each record in ActivitiesDetails always have both ActivitiesID and MovieID?

C: Why does this matter? What happens when the sequence exceeds 9999? There is no reason for users to even be aware of autonumber primary key.
http://blogs.office.com/b/microsoft-...er-than-1.aspx

D: You can use lookups in table but most developers don't favor table lookups. If there will be multiple users of this db really should use forms to interface with data instead of working directly with tables.

E: Use input mask - Access Help has guidelines.

[orange]

You seem to have all the info you need.
If it is a refresher tutorial that works from business facts to normalized database, then work through this tutorial
http://www.rogersaccesslibrary.com/T...lationship.zip

[butterbescotch]

@June7

A. Will keep note for that.
B. Ideally, yes. For instance, if we have an Weekly Film Viewing Activity, I basically want to know what films was shown (MovieID) and I also want to know the attendance of the members (ActivitiesID) Or should the ActivitiesID be replaced by the MembersID, but that would make new record for every member in one activity. So if the activity has an attendance of 10 people, I will have to make another record of 10. Am I correct?
C. Okay, maybe I'm being too hysterical, but it would be nice to start it with a four digit. No particular reason.
D. Can forms generate something that is not in the table itself?
E. Input Mask. Great!

@orange
Thanks for the link mate! Appreciate it :]

[June7]

D. Not sure what you mean. When I said not to use lookups in tables, this meant don't set up fields in table as a combobox with RowSource. Do this on forms.