I know there are a million schools of thought on design structure, so
I'm not trying to argue here, but I'd like to make some comments.
> A few comments on Trevor's DB structure recommendations regarding
> primary keys.
>
> 1) Only make the auto-incrementing primary key IF you don't
> already h
A few comments on Trevor's DB structure recommendations regarding
primary keys.
1) Only make the auto-incrementing primary key IF you don't already have
a unique identifier for each item in the table. Your church probably
doesn't have existing unique IDs for each member (or maybe you do -
memb
I'd say Medium because of your learning curve. The code
> itself is pretty reusable and small. Your basically adding
> data to a DB and retrieving it, no heavy processing.
>
> aaron wagner
>
>
>
> > -----Original Message-
> > From: Chris Olla
From: Chris Ollar [mailto:[EMAIL PROTECTED]
> > Sent: October 15, 2004 10:51
> > To: [EMAIL PROTECTED]
> > Subject: [PHP-WIN] Church Database
> >
> >
> > I realize this is asking a bunch but here we go...
> >
> > The local church I belong to wants t
> The church has about 2000 members. The groups can range in
> membership from
> as few as 5 to as many as 300.
>
> I'm a novice programmer and was looking into using MySQL and PHP to
> implement the system.
>
> Am I on the right track?
> Any thoughts or suggestions?
> Me being a beginner am I g
I realize this is asking a bunch but here we go...
The local church I belong to wants to implement a web based database so that
we can track attendance of our various groups that meet outside the church.
We want our group leaders to be able to add/delete/modify names and contact
information for t
