Re: massive MySQL tables

"Alfredeen, Johan" wrote: > You could normalize the db schema into several tables with fewer fields. > This way though, you probably need to keep track of the transaction and > commit the entire session or nothing at all. Yeah, there's a catch. The form IS very long-winded and it WILL take time to fill in, so they've asked for the form to be "saveable" half-complete. I think this is getting messy when you start to think about multiple tables, some complete, some incomplete, etc etc. Yuk!! > I hope you have split the form up into several pages. Personally, I hate > when websites ask for tons of fields to be filled in on a single page. As a > rule of thumb, any one page should not take more than 10-15 minutes max for > a visitor to complete, IMHO. I know -- same here, but the nature of this form is that they will prolly look at it two or three times, then finally complete it, possibly copying and pasting from other programs. With the "save this form for later" feature, I think it's safe to keep the form on one page, so they can prepare everything before hand. Plus, I'd like to keep development time to a minimum without cutting corners. Thanks for your help. Justin