Sorry, got in a hurry, sending this as is.
Get your database schema (this is the "map" of the database).
1. Setup the connection in DW
2. Create a recordset for the table to insert or edit data
http://cdcdigital.com/vids/DynamicContent/DynamicContent.html
3. Create a form for the data, putting a new field for every
field in the
table in the database schema
4. Use the DW Behaviors and Insert Record Behavior
5. You should now be able to insert data into your database.
This is from an email I wrote a few days ago about creating
an update form
for somebody that already had an entry form:
Re-use your form from your entry page. Save it as page-edit
or whatever and
then remove the server behavior for insert record. Then apply
the update
record field to it. You can redirect to whatever page you
choose, I
typically have it redirect to the same page, in case I want
to do multiple
updates.
Copy your edit recordset (calling it rsEdit) and rename it
rsList. You will
use this recordset to feed the title and id of your documents
to be edited
to your list, which will select which doc to edit.
Create a new form above your existing Update form. Insert a
list. Feed the
rsList recordset into this, having it retain the ID and
display the Title.
Put the form action to this page.
Change your insert rsEdit recordset to capture a variable
from a form (the
ID would be the best).
Now, apply a show/hide behavior to your List. Show if rsEdit
is empty
(which it will be until you feed it the variable from the
form).
Apply a show/hide behavior to your Edit form. Show if rsEdit
is NOT empty.
Let me know how that works. It's from memory and not a
"walk-through" so it
might not be 100% accurate.
"tiger2808" <webforumsuser@macromedia.com> wrote in
message
news:e42skn$luu$1@forums.macromedia.com...
> This just got infinitely more complicated! I think.
>
> How do other small designers do it? Do they tell the
customer - NO you
> can't
> do the updates yourself?
>
> I can't imagine I am the only person to have ever been
in this situation.
>
> ??
>
>
>