/t5/dreamweaver-discussions/return-to-updated-record/td-p/221813Aug 25, 2007
Aug 25, 2007
Copy link to clipboard
Copied
I created an update page awhile back and used Dreamweaver to
write the code. The update is successful, but the index is set to
the beginning of the recordset when completed. I can't seem to find
where this is happening...any suggestions?
/t5/dreamweaver-discussions/return-to-updated-record/m-p/221814#M169372Aug 26, 2007
Aug 26, 2007
Copy link to clipboard
Copied
eacollie1 wrote:
> I created an update page awhile back and used
Dreamweaver to write the code.
> The update is successful, but the index is set to the
beginning of the
> recordset when completed. I can't seem to find where
this is happening...any
> suggestions?
--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of
ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/
/t5/dreamweaver-discussions/return-to-updated-record/m-p/221815#M169373Aug 26, 2007
Aug 26, 2007
Copy link to clipboard
Copied
Thank you David.
I guess I'm not sure what the code is doing in Dreamweaver.
It created a form and a navigation series of buttons (first,
previous, next, and last). I created a button for editing the
existing record and, when the user clicks this button, it redirects
to the form and runs an update statement. This works and the record
is updated; however, it goes back to the first record in the
recordset.
/t5/dreamweaver-discussions/return-to-updated-record/m-p/221816#M169374Aug 26, 2007
Aug 26, 2007
Copy link to clipboard
Copied
eacollie1 wrote:
> Perhaps I should make a separate edit page?
Yes, I think so. The normal way is to create a list of all
records,
together with links to update and delete forms. If a separate
form
handles the update, you can redirect the user to wherever you
want
afterwards.
--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of
ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/