Re: Too many database headers?

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 50968
interpreted = N
texte = > When this form is completely filled out and submitted (try if you want > to -- not writing to a .db yet, just dumping [formvariables] onto the > landing page for testing... use fake info, I don't care.) it returns > almost 200 [formvariables]... Is this too many db headers? > Server/memory is fine (robust, etc.)... If so, I could obviously group > many of them together and extract using [listwords] or whatever...>> My gut feeling is that everything will be just fine, but I wanted to > check with y'all first.I once built an intranet site for a customer, where the header in the database was almost 600 fields wide. Since each individual record could have that much data associated with it, we determined that it was easier to create the massively wide database, as opposed to creating various databases with parts of each record in it. Other than the unwieldyness of working with the large database (Excel '97 and BBEdit 4.x wouldn't go that wide), we had no problems whatsoever (other than the fact that the customer stiffed us 4 Grand). We did find that it made it so much easier during construction of the site to use .hdr files, since we could just add the fields to that file, and not worry about opening the whole database.Dennis-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: Too many database headers? (Dan Strong 2003)
Re: Too many database headers? (Dennis J. Bonsall, Jr. 2003)
Re: Too many database headers? (Dan Strong 2003)
Too many database headers? (Dan Strong 2003)

> When this form is completely filled out and submitted (try if you want > to -- not writing to a .db yet, just dumping [formvariables] onto the > landing page for testing... use fake info, I don't care.) it returns > almost 200 [formvariables]... Is this too many db headers? > Server/memory is fine (robust, etc.)... If so, I could obviously group > many of them together and extract using [listwords] or whatever...>> My gut feeling is that everything will be just fine, but I wanted to > check with y'all first.I once built an intranet site for a customer, where the header in the database was almost 600 fields wide. Since each individual record could have that much data associated with it, we determined that it was easier to create the massively wide database, as opposed to creating various databases with parts of each record in it. Other than the unwieldyness of working with the large database (Excel '97 and BBEdit 4.x wouldn't go that wide), we had no problems whatsoever (other than the fact that the customer stiffed us 4 Grand). We did find that it made it so much easier during construction of the site to use .hdr files, since we could just add the fields to that file, and not worry about opening the whole database.Dennis-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Dennis J. Bonsall, Jr.

DOWNLOAD WEBDNA NOW!

Re: Too many database headers?

2003

Top Articles:

Related Readings: