Shane,
I don't have any books to recommend. I have some of the same ones you
mentioned but I don't have any reference books. I just find myself using
google and the forums for most of this type of stuff.
If you find a good one please let me know!
--
Sincerely,
S. Justin Gengo, MCP
Web Developer / Programmer
Free code library at:
www.aboutfortunate.com
"Out of chaos comes order."
Nietzche
"D. Shane Fowlkes" <shanefowlkes@h-o-t-m-a-i-l.com> wrote in message
news:%23QUePw99DHA.1816@TK2MSFTNGP12.phx.gbl...[color=blue]
> Yeah! Thanks! Boy that was easy.
>
> I seem to have trouble remembering all the attributes, namespaces, etc for
> all this .NET stuff. Is there a good book which documents and diagrams all
> this stuff out? I have ASP.NET Unleashed by SAMS but I'd like to get my
> hands on some good reference "charts" and diagrams which show ALL the
> attributes for ALL the web controls, etc....
>
> =)
>
>
> "S. Justin Gengo" <sjgengo@aboutfortunate.com> wrote in message
> news:%230s2ZL89DHA.1768@TK2MSFTNGP09.phx.gbl...[color=green]
> > Shane,
> >
> > You'll love how easy this is!
> >
> > On your delete button just set it's "CausesValidation" property to[/color][/color]
false.[color=blue][color=green]
> > Then it won't trigger the validators.
> >
> > --
> > Sincerely,
> >
> > S. Justin Gengo, MCP
> > Web Developer / Programmer
> >
> > Free code library at:
> >
www.aboutfortunate.com
> >
> > "Out of chaos comes order."
> > Nietzche
> >
> >
> > "D. Shane Fowlkes" <shanefowlkes@h-o-t-m-a-i-l.com> wrote in message
> > news:OjRgqz79DHA.340@tk2msftngp13.phx.gbl...[color=darkred]
> > > Sorry for the length of this post.
> > >
> > > I have created a rather complex form which has a header/line item[/color][/color]
> (parent[color=green][color=darkred]
> > > and child records) structure. It's for an intranet. A screenshot can[/color][/color]
> be[color=green][color=darkred]
> > > seen here:
http://www.drpt.virginia.gov/temp1.gif All the fields on[/color][/color]
> this[color=green][color=darkred]
> > > form have validation controls on them so they can not submit the form[/color]
> > unless[color=darkred]
> > > all fields are completed and some fall within a specified numeric[/color][/color][/color]
range.[color=blue][color=green][color=darkred]
> > >
> > > When the form first is loaded, there are two buttons as shown in the[/color][/color]
> link[color=green][color=darkred]
> > > above that are disabled by default. They become enabled once the form[/color][/color]
> is[color=green][color=darkred]
> > > submitted.
> > >
> > > Here's the basic concept. The user fills out the form and clicks Save[/color]
> > Data.[color=darkred]
> > > The form is using ViewState so when the form is submitted (Save Data),[/color][/color]
> the[color=green][color=darkred]
> > > page posts to itself and the data "sticks" in the fields. The Save[/color][/color][/color]
Data[color=blue][color=green][color=darkred]
> > > button fires a sub routine which writes the data in the top section of[/color][/color]
> the[color=green][color=darkred]
> > > form to one table and the "line item" section to another table. When[/color][/color]
> the[color=green][color=darkred]
> > > data is successfully saved as shown in
> > >
http://www.drpt.virginia.gov/temp2.gif, a confirmation label is shown[/color][/color][/color]
on[color=blue][color=green]
> > the[color=darkred]
> > > page and a DataGrid displays the new line item. The user can then add[/color][/color][/color]
a[color=blue][color=green][color=darkred]
> > > second, third or however many line items by simply filling in the[/color][/color][/color]
fields[color=blue][color=green][color=darkred]
> > > (and even changing the header information if needed) and clicking Save[/color]
> > Data[color=darkred]
> > > each time. My sub successfully works and each time the page "loads",[/color][/color]
> the[color=green][color=darkred]
> > > DataGrid gets a new row (image only shows one). So far, so good.
> > >
> > > The thought behind this structure is that the user needs to able to[/color][/color]
> enter[color=green]
> > in[color=darkred]
> > > multiple line items as needed, so here I'm letting them add them one[/color][/color][/color]
at[color=blue]
> a[color=green][color=darkred]
> > > time instead hard coding X number of blank line items ...X number of[/color][/color]
> rows[color=green]
> > of[color=darkred]
> > > form fields (the validation for that would be a nightmare).
> > >
> > > All works fine. Once the SaveData sub is fired, I set a variable in
> > > ViewState and enable the two additional buttons at the button and[/color][/color][/color]
change[color=blue][color=green]
> > my[color=darkred]
> > > INSERT statement to UPDATE statement for the header data. One of the[/color]
> > newly[color=darkred]
> > > enabled buttons is a "Delete" button. I wanted to allow the user to[/color]
> > Delete[color=darkred]
> > > all the records and start over with a fresh form.
> > >
> > > Here's the problem (finally): My delete sub works just fine but by[/color]
> > clicking[color=darkred]
> > > the "Delete" button causes the form to post and all of the field[/color]
> > validators[color=darkred]
> > > are triggered. Instead of deleting the data and refreshing the page[/color][/color][/color]
as[color=blue]
> my[color=green][color=darkred]
> > > sub should do, I'm prompted to provide data in all the required[/color][/color][/color]
fields![color=blue][color=green]
> > In[color=darkred]
> > > short, my form thinks my delete button is a submit button instead of[/color][/color]
> just[color=green]
> > a[color=darkred]
> > > plain button.
> > >
> > > Is there anyway to work around this? I see that you cannot define[/color][/color]
> exactly[color=green][color=darkred]
> > > what TYPE of button it is using asp:button such as type="button" or
> > > type="submit". So how can I use a button to call my DeleteRecords sub
> > > without being pestered by the form validation controls?
> > >
> > > TIA!!!
> > >
> > > -Shane
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]
