Hello,

I'm quite new to ASP, but being a programmer with a good experience, I manage to do the ASP job too.
Still, I can't know if I'm efficient enough or not.
Please write me a rough estimation of time needed to develop an ASP input form , containing a lot of fields (255). The form is big enough, to be splitted in 4 steps (I don't want to create a page this big)

So the question is in fact how much time should I need to do this:
- create the input form (considering that I have to choose a design to match an existing ASP site, to which this form is added; I have all ASP files of the site, but it's big, and it is the first time I see them)
- create the SQL table for the form
- the form is to save data, and later edit too (based on a login process)

thank you

255 fields? That's messed up. What the hell could you need to fill 255 fields of info?

I'd say 7-8 hours, and probably more than 4 steps.

Well...it took me longer
But maybe that's OK for a start, and maybe I'm not using the right tools (which editor are you using ?)
By the way: for saving the fields in the database, at the final step, is there any other way than to keep values in session ? There is no problem because they are so many ?

thanks again

HomeSite 5 (it's an older colour-coded text editor, but it does the job for me). I've also built precompiled functions for form generation and data retrieval/manipulation.

What I do with a multi-part form is that I generate a record after the first step. Even if all the remaining fields are blank, that's fine. All I want is the unique identifier (usually an AutoNumber field) from the record itself.

That's what I make the session variable. Nothing else. That way, it's tied into the record and can retrieve it all as i see fit.

<sputter> 255! WOW! That has got to be a record.

I am with ADAM, don't waste time storing that info in session, drop it into the DB after each page, then you will have at least partial info (make sure to grab the important stuff on the first page) in the event the user decides the form is way too friggin long.

Just curious, what is the form for?

It isn't your editor that is going to kill you on this one amigo, it is the hand coding of all those fields.

Like A, I have functions pre-built that simply allow me to enter field type, name, mask, order, (You'd have to do page as well) etc. into a table, and then I let the script generate the individual fields for each page. Build that functionality and you won't ever have to wonder how long it will take, it will only be th etime needed to enter the fields into your list in the DB.

YM

Use DB to hold value this huge Session will make your WebServer DIE