Re: [GENERAL] Allowing Custom Fields

2006-01-27 Thread Bruno Wolff III
On Fri, Jan 27, 2006 at 10:40:05 -0600, Aaron Colflesh <[EMAIL PROTECTED]> wrote: > Bruno Wolff III wrote: > >On Fri, Jan 27, 2006 at 10:25:00 -0600, > > Aaron Colflesh <[EMAIL PROTECTED]> wrote: > > > >>#2 would seem to be the simplest except I'm really not too keen on the > >>idea of manipu

Re: [GENERAL] Allowing Custom Fields

2006-01-27 Thread Uwe C. Schroeder
On Friday 27 January 2006 08:25, Aaron Colflesh wrote: > Hello folks, > I've run into a challenge that doesn't appear to have been discussed in > the archives anywhere. > > I'm designing a database that users need to have the ability to > customize some. They just need the ability to add extra fiel

Re: [GENERAL] Allowing Custom Fields

2006-01-27 Thread Aaron Colflesh
Bruno Wolff III wrote: On Fri, Jan 27, 2006 at 10:25:00 -0600, Aaron Colflesh <[EMAIL PROTECTED]> wrote: #2 would seem to be the simplest except I'm really not too keen on the idea of manipulating a table like that on the fly (even though I did proof of concept it and it seems

Re: [GENERAL] Allowing Custom Fields

2006-01-27 Thread Bruno Wolff III
On Fri, Jan 27, 2006 at 10:25:00 -0600, Aaron Colflesh <[EMAIL PROTECTED]> wrote: > > #2 would seem to be the simplest except I'm really not too keen on the > idea of manipulating a table like that on the fly (even though I did > proof of concept it and it seems to be simple enough to be fairl

[GENERAL] Allowing Custom Fields

2006-01-27 Thread Aaron Colflesh
Hello folks, I've run into a challenge that doesn't appear to have been discussed in the archives anywhere. I'm designing a database that users need to have the ability to customize some. They just need the ability to add extra fields to an existing table (oh and they can't touch the predefin