The steps in the process are listed in an SQL Server table. I would assume a bit (0,1) field needs to be created to accept the checks.

My question is can a single asp page handle this or do I need to break it out to separate submit/results pages?

------------------
Siegfried

I would envisage a page with check boxes, each of which is populated with a true / false from the DB

<input type=checkbox Name=Column <%If rs("Column") then Response.write "checked"%>>

Clearing the page would just mean deleting the record?

------------------
Spooky
"I am Spooky of Borg. Prepare to be assimilated, babycakes!"
Subscribe to OutFront News
Database / DRW Q & A
The Spooky Login!

[This message has been edited by Spooky (edited 03-04-2001).]

Yes, I believe I have over-complicated this, but would like to better understand what your thinking.

1. Would this be a single asp page (i.e., no results page)?

2. I made an asp page with a two column table. The right column contains the text of the process. The left column contains check boxes with submit and reset buttons.

3. When I click on Form Properties and point to a database, FP builds a nice little database in fpdb with C1 populated with ON.

4. When I run the asp page, I get a confirmation page sent back to me. So far this is all default FrontPage Form directed-to-database procedure.

5. What do I need to do to make your idea work? Based on what I've described so far, instead of having a confirmation page come back to me, I just need the same asp page refreshed with the box I just checked populated with a check in it.

6. Ideally, I'd get rid of the reset button next to each checkbox and just use a single one at the bottom of the page to reset the entire recordset to OFF.

Can you point me in the right direction?

Thanks a bunch...

------------------
Siegfried

Spooky, the page you envision is a single asp page that updates itself - not output to a results page?

------------------
Siegfried

You would have a query page, listing all of the records, linking to the individual records - basic DRW stuff

You would have a results page, showing the unique record.

An update button at the bottom, would post to another DRW page (with update SQL) that would change the values

On page 2, you would check / remove checks before saving. Perhaps add a field "complete / In progress" so you can tell what stage its at too?

"reset button next to each checkbox" ??

Are each checkbox a form in itself? They should all be part of one form

------------------
Spooky
"I am Spooky of Borg. Prepare to be assimilated, babycakes!"
Subscribe to OutFront News
Database / DRW Q & A
The Spooky Login!

I tried this: mypage.asp with a check box and submit button. The Form Property points to Custom Script and Form Name is mypage.asp. Under Form Properties>Options, I entered mypage.asp under Action. The text of what this check box refers to is just plain old html located next to the checkbox. This way I don't have to load text into a database.

When I run this asp and click the checkbox, then submit, the asp page refreshes itself. However, the box comes back unchecked. If I could get the action to return the page with the box checked, I could do this whole exercise with only one asp page!

Can you think of what I can do to get the check to stick in the checkbox without resorting to an on/off DB solution?

Hey, thanks for your brainpower, here...

------------------
Siegfried

<input type='checkbox' Name='C1' Value ='Yes' <%If Request.Form("C1") = "Yes" then Response.write "checked"%>>

Id do it on one ppage in asp, but using the DRW, you have to make allowances. I wasnt sure which you were trying

------------------
Spooky
"I am Spooky of Borg. Prepare to be assimilated, babycakes!"
Subscribe to OutFront News
Database / DRW Q & A
The Spooky Login!

However, when I add the next checkbox below the first one (next step in the process), if I click it, the first box's check disappears. This process is 12-15 steps long and I want to keep checking things off, then when the entire task is done, reset them all to the unchecked condition.

Will I still be able to do this on one asp page?

------------------
Siegfried