On Fri, 2009-02-13 at 08:02 -0500, Al wrote:
>
> Rene Veerman wrote:
> > Al wrote:
> >> I'm scripting a light-weight, low volume signup registry for a running
> >> club. Folks sign up to volunteer for events and the like. There will
> >> generally be a handful of signup registries at any one ti
> I'm scripting a light-weight, low volume signup registry for a running club.
> Folks sign up to volunteer for events and the like. There will generally be
> a handful of signup registries at any one time. A typical registry will only
> contain 50 to 100 names. Each registry is only in existence
Rene Veerman wrote:
Al wrote:
I'm scripting a light-weight, low volume signup registry for a running
club. Folks sign up to volunteer for events and the like. There will
generally be a handful of signup registries at any one time. A typical
registry will only contain 50 to 100 names. Each
Al wrote:
I'm scripting a light-weight, low volume signup registry for a running
club. Folks sign up to volunteer for events and the like. There will
generally be a handful of signup registries at any one time. A typical
registry will only contain 50 to 100 names. Each registry is only in
ex
Al wrote:
> I'm scripting a light-weight, low volume signup registry for a running
> club. Folks sign up to volunteer for events and the like. There will
> generally be a handful of signup registries at any one time. A typical
> registry will only contain 50 to 100 names. Each registry is only i
tedd wrote:
At 3:26 PM -0500 2/12/09, Al wrote:
I'm scripting a light-weight, low volume signup registry for a running
club. Folks sign up to volunteer for events and the like. There will
generally be a handful of signup registries at any one time. A typical
registry will only contain 50 to
Robert Cummings wrote:
On Thu, 2009-02-12 at 15:45 -0500, Al wrote:
Robert Cummings wrote:
On Thu, 2009-02-12 at 15:26 -0500, Al wrote:
I'm scripting a light-weight, low volume signup registry for a running club.
Folks sign up to volunteer for events and the like. There will generally be a
At 3:45 PM -0500 2/12/09, Al wrote:
Robert Cummings wrote:
By writing this email you've already spent about as much time as it
would take to set up an SQL database and just start coding.
Cheers,
Rob.
True, but, the website is on a shared host which means someone must
setup and maintain the D
> True, but, the website is on a shared host which means someone must setup
> and maintain the DB and my code has to create and remove tables, as needed.
> Plus, someone must keep the login parms in sync between the DB and my code.
>
> Al
>
Sound more like a hosting problem than a database pro
On Thu, 2009-02-12 at 15:45 -0500, Al wrote:
>
> Robert Cummings wrote:
> > On Thu, 2009-02-12 at 15:26 -0500, Al wrote:
> >> I'm scripting a light-weight, low volume signup registry for a running
> >> club.
> >> Folks sign up to volunteer for events and the like. There will generally
> >> be
Robert Cummings wrote:
On Thu, 2009-02-12 at 15:26 -0500, Al wrote:
I'm scripting a light-weight, low volume signup registry for a running club.
Folks sign up to volunteer for events and the like. There will generally be a
handful of signup registries at any one time. A typical registry will
At 3:26 PM -0500 2/12/09, Al wrote:
I'm scripting a light-weight, low volume signup registry for a
running club. Folks sign up to volunteer for events and the like.
There will generally be a handful of signup registries at any one
time. A typical registry will only contain 50 to 100 names. Eac
On Thu, 2009-02-12 at 15:26 -0500, Al wrote:
> I'm scripting a light-weight, low volume signup registry for a running club.
> Folks sign up to volunteer for events and the like. There will generally be
> a
> handful of signup registries at any one time. A typical registry will only
> contain 5
13 matches
Mail list logo
