Re: Re: massive MySQL tables

Hi all, Thanks for the comments / help. I've decided to "walk before running", starting with the most simple solution possible (85 fields per row, single page form) to do some testing. If it works out, i'm happy, if not I know I have invest some more time/money. In discussion with the client, we determined that the application itself will NOT get many hits -- they can imagine a MAXIMUM of 30 applications per week, so we're really talking about 2 hits per hour, not 2 per minute. I've also made a point of NOT indexing many fields, since this will cause a performance hit on writing / modifying, and we'll establish WHICH fields need indexing over the coming months. So, as long as the HTML renders fast enough, I think i'm okay for the monent :) But some testing will tell the full story in the coming weeks! Justin