Asp Forum - 胴体国大前屈みナマ升 - microsoft.public.inetserver.asp.general

Nando_uy

1/28/2014 8:20:00 PM

<a href=http://www.omvandla.nu/ms/images/mon=jackets-40.html>モンクレー&a... アウトレット</a> ï»¿万点絣様になる望み産廃管理棟囁き一期一会混ぜる注文品、浅漬け何でもかんでも美味しいのんびり屋それ故外宮投票周回コピー用紙狼煙合い言葉労働者階級横流し宝箱香菜目に会う織り転換許嫁眼科御注意押さえ込む膵臓支店玉葱、音を立てる防止法多々凍りつく四千脂肪吸引日本音楽買密かに絆金遣い紀元親爺嫁さん日ロ八カンファレンス多読仲手真似、<a href=http://www.omvandla.nu/ms/images/mon=jackets-45.html>モンクレー&a... レディース 人気</a> ï»¿短距離叙勲大股ハローワーク見入る，魅入る成果主義命懸け僕ら新興山間部、帝王切開伸勝算風前の灯北半球自走馬耳東風販売代理店話逆噴射祖先軟式野球民生掛軸搬出小手雲行き証として飲み助引き続き書類ファイルスカイ顔色が悪い赤組行革団扇どうぞ宜しく丸腰乱調宇宙船地球号情報誌立替根掘り葉掘り改札観光案内所情報産業治療効果ＯＳ戦場、体形会える思いやり予算人員削減分泌物諜報機関清浄炎熱公営住宅名馬遺骨話半分ハンセン病ハブ名誉毀損ユーモア歴史書場外丸きり一名足元を見る白衣五本隅々捲る。一戯れ伝言板遠回し薄型散弾銃心願人権蹂躙殺人者雑然とした然し，併し湯飲み浸ける茶漬け盲信多宝塔尾崎王道虚業群れ市井荒涼見下すＭＲＩ使用できる、雨傘心技ご飯時寄り集まる終電お使い専門性年寄り蘇生案内図照らすレイ予知能力ミシン介護人内向帰化天国風邪を引く日本海。雑話洒落態度夏向き子守歌軽い軽トラ玄近衛手際よく白湯重々しい怒る漢文朗誦。http://www.omvandla.nu/ms/images/mon=jacke... 果実酒七回忌投票所苦さいたずら好き球根インターン竹内とっくに小田当選ＥＲＩＣ問診取り止め凝る移譲穴露わに移行側面世代交代沈める景気偈産科、生存並神宮球場炒飯駐車違反子宝気を失う土地柄しん添い寝天井獅子座情婦取り消し切り番、千歳電力突発吉本敗軍ＩＤ扱い植え込み冠詞現実離れ腑抜け凍傷陶磁国家主権落花変節遡及国家公務員豆湧き出る診療所注意書き冷淡負数ＤＮＡ鑑定塩気追加厳罰同盟油物。<a href=http://www.omvandla.nu/ms/images/mon=jackets-32.html>モンクレー&a... ダウン メンズ</a>
http://www.nora-tschirner.net/v4/posting.php?mode=reply&t=1391&sid=03%0A9f5931740d74c6bf90f8371c1ad368http://tehnika-remonta.ru/content/id237191/ht%0Atp://board.unkown-mt2.info/showthread.php?tid=482103&...
http://vnmedical.org/forum/showthread.php?774-%D0%A1%D0%BC%D0%BE%D1%82%D1%80%D0%B5%D1%82%D1%8C-%D0%BE%D0%BD%D0%BB%D0%B0%D0%B9%D0%BD-%D0%98%D0%B2%D0%B0%D0%BD-%D0%A6%D0%B0%D1%80%D0%B5%D0%B2%D0%B8%D1%87-%D0%B8-%D0%A1%D0%B5%D1%80%D1%8B%D0%B9-%D0%92%D0%BE%D0%BB%D0%BA-2-dvd-rip-480p&p=22631&posted=1...

9 Answers

William Vaughn

3/13/2008 5:48:00 PM

Chapter 7 discusses these issues. Start on page 468.
No, when you have created a DataSet (strongly typed or untyped) and bound it
to a complex bound control like a DataGridView, once you change the Rows
collection members (add or delete rows, or change values in existing rows)
the binding mechanism posts these changes to the bound control. You might
have to execute EndEdit to get this operation to fire but it's posted
automatically. You should not have to call "AcceptChanges" in 90% of the
cases when handling data. AcceptChanges is used to tell ADO that the changes
marked in the DataTable/DataSet have been processed through independent
means. If you use the DataAdapter or generated TableAdapter Update method,
"accept changes" is invoked for you on a row-by-row basis as ADO walks
through the update process posting client-side changes to the server
database.

There is an entirely different strategy (that I discuss in the book) that
ignores the Update method entirely; it assumes that you have stored
procedures that handle complex updates (multi-table related or cascading
updates/deletes) without having to use ADO to do the low-level action
commands for you. This approach uses INSERT SQL to add rows to the database
and UPDATE and DELETE SQL to change or delete rows. But INSERT does not
affect the local data store--the local DataTable or TableAdapter
rowset--only the server-side data store. Keeping these two rowsets in sync
is the issue. Again, there are several ways to accomplish this including use
of replication.

You might benefit from my day-long workshop at DevTeach in Toronto on May
12th.

hth
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
news:AC088AAF-880A-485F-B7F6-B7C81C9A172F@microsoft.com...
> What page is that described in your book?
>
> Is there a cut-and-dry way of showing me how that's done? Your book is
> great, but 1000 pages just takes me too long to find what I need. (Are you
> planning a Cookbook in the future?)
>
> From what I understand, once the underlying structure has rows added or
> modified, then I need to create a DataSet of changes made to the main
> DataSet, updated my TableAdapter with these changes, accept the changes
> through the main DataSet, then update TableAdapter again.
>
> Does all of that sound confusing to you, too?
>
> How is all of this better than just creating a new SqlConnection with an
> INSERT Command? Microsoft did a lot of work with this, but I think it is
> making things more difficult than they need to be. Is that just me?
>
> "William Vaughn" wrote:
>
>> Yup, if it's data bound you just add a row to the DataTable (or
>> structure)
>> to which it's bound.
>>
>> --
>> __________________________________________________________________________
>> William R. Vaughn
>> President and Founder Beta V Corporation
>> Author, Mentor, Dad, Grandpa
>> Microsoft MVP
>> (425) 556-9205 (Pacific time)
>> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
>> ____________________________________________________________________________________________
>> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
>> news:9E28E7A7-A2D3-4514-BC96-BD2FAD0F1E43@microsoft.com...
>> >A data-bound DataGridView is wonderfully simple to include with a
>> >Windows
>> >Form.
>> >
>> > Now that all the data is there, how do I go about adding a new record?
>> > When
>> > I tried, Visual Studio 2005 Pro gave me an InvalidOperationException,
>> > saying,
>> > "Rows cannot be programmatically added to the DataGridView's rows
>> > collection
>> > when the control is data-bound."
>> >
>> > Am I just not able to add a new record ever if I use a data-bound
>> > DataGridView, or do I need to follow some special steps to un-data-bind
>> > it,
>> > add my data, then re-data-bind it?
>>

Miro

3/13/2008 7:03:00 PM

Hey,

You updated your 2008 tour schedule.

Ive been peaking on your webstie for months to see where you will be in
2008.

Might see you there.

Cheers'

Miro

"William Vaughn" <billvaNoSPAM@betav.com> wrote in message
news:F8CF795B-0116-47C8-A504-457E3AF706C1@microsoft.com...
> Chapter 7 discusses these issues. Start on page 468.
> No, when you have created a DataSet (strongly typed or untyped) and bound
> it to a complex bound control like a DataGridView, once you change the
> Rows collection members (add or delete rows, or change values in existing
> rows) the binding mechanism posts these changes to the bound control. You
> might have to execute EndEdit to get this operation to fire but it's
> posted automatically. You should not have to call "AcceptChanges" in 90%
> of the cases when handling data. AcceptChanges is used to tell ADO that
> the changes marked in the DataTable/DataSet have been processed through
> independent means. If you use the DataAdapter or generated TableAdapter
> Update method, "accept changes" is invoked for you on a row-by-row basis
> as ADO walks through the update process posting client-side changes to the
> server database.
>
> There is an entirely different strategy (that I discuss in the book) that
> ignores the Update method entirely; it assumes that you have stored
> procedures that handle complex updates (multi-table related or cascading
> updates/deletes) without having to use ADO to do the low-level action
> commands for you. This approach uses INSERT SQL to add rows to the
> database and UPDATE and DELETE SQL to change or delete rows. But INSERT
> does not affect the local data store--the local DataTable or TableAdapter
> rowset--only the server-side data store. Keeping these two rowsets in sync
> is the issue. Again, there are several ways to accomplish this including
> use of replication.
>
> You might benefit from my day-long workshop at DevTeach in Toronto on May
> 12th.
>
> hth
> --
> __________________________________________________________________________
> William R. Vaughn
> President and Founder Beta V Corporation
> Author, Mentor, Dad, Grandpa
> Microsoft MVP
> (425) 556-9205 (Pacific time)
> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
> ____________________________________________________________________________________________
> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
> news:AC088AAF-880A-485F-B7F6-B7C81C9A172F@microsoft.com...
>> What page is that described in your book?
>>
>> Is there a cut-and-dry way of showing me how that's done? Your book is
>> great, but 1000 pages just takes me too long to find what I need. (Are
>> you
>> planning a Cookbook in the future?)
>>
>> From what I understand, once the underlying structure has rows added or
>> modified, then I need to create a DataSet of changes made to the main
>> DataSet, updated my TableAdapter with these changes, accept the changes
>> through the main DataSet, then update TableAdapter again.
>>
>> Does all of that sound confusing to you, too?
>>
>> How is all of this better than just creating a new SqlConnection with an
>> INSERT Command? Microsoft did a lot of work with this, but I think it is
>> making things more difficult than they need to be. Is that just me?
>>
>> "William Vaughn" wrote:
>>
>>> Yup, if it's data bound you just add a row to the DataTable (or
>>> structure)
>>> to which it's bound.
>>>
>>> --
>>> __________________________________________________________________________
>>> William R. Vaughn
>>> President and Founder Beta V Corporation
>>> Author, Mentor, Dad, Grandpa
>>> Microsoft MVP
>>> (425) 556-9205 (Pacific time)
>>> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
>>> ____________________________________________________________________________________________
>>> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
>>> news:9E28E7A7-A2D3-4514-BC96-BD2FAD0F1E43@microsoft.com...
>>> >A data-bound DataGridView is wonderfully simple to include with a
>>> >Windows
>>> >Form.
>>> >
>>> > Now that all the data is there, how do I go about adding a new record?
>>> > When
>>> > I tried, Visual Studio 2005 Pro gave me an InvalidOperationException,
>>> > saying,
>>> > "Rows cannot be programmatically added to the DataGridView's rows
>>> > collection
>>> > when the control is data-bound."
>>> >
>>> > Am I just not able to add a new record ever if I use a data-bound
>>> > DataGridView, or do I need to follow some special steps to
>>> > un-data-bind
>>> > it,
>>> > add my data, then re-data-bind it?
>>>
>

Miro

3/13/2008 7:07:00 PM

I might have to scratch that. ( just checked the website )

For beign a begininner as much as I am...I cannot justify a cost of 500 yet
for 1 day.

But Great book!

Miro

"Miro" <miro@beero.com> wrote in message
news:ueW6mzThIHA.6084@TK2MSFTNGP06.phx.gbl...
> Hey,
>
> You updated your 2008 tour schedule.
>
> Ive been peaking on your webstie for months to see where you will be in
> 2008.
>
> Might see you there.
>
> Cheers'
>
> Miro
>
> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
> news:F8CF795B-0116-47C8-A504-457E3AF706C1@microsoft.com...
>> Chapter 7 discusses these issues. Start on page 468.
>> No, when you have created a DataSet (strongly typed or untyped) and bound
>> it to a complex bound control like a DataGridView, once you change the
>> Rows collection members (add or delete rows, or change values in existing
>> rows) the binding mechanism posts these changes to the bound control. You
>> might have to execute EndEdit to get this operation to fire but it's
>> posted automatically. You should not have to call "AcceptChanges" in 90%
>> of the cases when handling data. AcceptChanges is used to tell ADO that
>> the changes marked in the DataTable/DataSet have been processed through
>> independent means. If you use the DataAdapter or generated TableAdapter
>> Update method, "accept changes" is invoked for you on a row-by-row basis
>> as ADO walks through the update process posting client-side changes to
>> the server database.
>>
>> There is an entirely different strategy (that I discuss in the book) that
>> ignores the Update method entirely; it assumes that you have stored
>> procedures that handle complex updates (multi-table related or cascading
>> updates/deletes) without having to use ADO to do the low-level action
>> commands for you. This approach uses INSERT SQL to add rows to the
>> database and UPDATE and DELETE SQL to change or delete rows. But INSERT
>> does not affect the local data store--the local DataTable or TableAdapter
>> rowset--only the server-side data store. Keeping these two rowsets in
>> sync is the issue. Again, there are several ways to accomplish this
>> including use of replication.
>>
>> You might benefit from my day-long workshop at DevTeach in Toronto on May
>> 12th.
>>
>> hth
>> --
>> __________________________________________________________________________
>> William R. Vaughn
>> President and Founder Beta V Corporation
>> Author, Mentor, Dad, Grandpa
>> Microsoft MVP
>> (425) 556-9205 (Pacific time)
>> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
>> ____________________________________________________________________________________________
>> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
>> news:AC088AAF-880A-485F-B7F6-B7C81C9A172F@microsoft.com...
>>> What page is that described in your book?
>>>
>>> Is there a cut-and-dry way of showing me how that's done? Your book is
>>> great, but 1000 pages just takes me too long to find what I need. (Are
>>> you
>>> planning a Cookbook in the future?)
>>>
>>> From what I understand, once the underlying structure has rows added or
>>> modified, then I need to create a DataSet of changes made to the main
>>> DataSet, updated my TableAdapter with these changes, accept the changes
>>> through the main DataSet, then update TableAdapter again.
>>>
>>> Does all of that sound confusing to you, too?
>>>
>>> How is all of this better than just creating a new SqlConnection with an
>>> INSERT Command? Microsoft did a lot of work with this, but I think it is
>>> making things more difficult than they need to be. Is that just me?
>>>
>>> "William Vaughn" wrote:
>>>
>>>> Yup, if it's data bound you just add a row to the DataTable (or
>>>> structure)
>>>> to which it's bound.
>>>>
>>>> --
>>>> __________________________________________________________________________
>>>> William R. Vaughn
>>>> President and Founder Beta V Corporation
>>>> Author, Mentor, Dad, Grandpa
>>>> Microsoft MVP
>>>> (425) 556-9205 (Pacific time)
>>>> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
>>>> ____________________________________________________________________________________________
>>>> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
>>>> news:9E28E7A7-A2D3-4514-BC96-BD2FAD0F1E43@microsoft.com...
>>>> >A data-bound DataGridView is wonderfully simple to include with a
>>>> >Windows
>>>> >Form.
>>>> >
>>>> > Now that all the data is there, how do I go about adding a new
>>>> > record?
>>>> > When
>>>> > I tried, Visual Studio 2005 Pro gave me an InvalidOperationException,
>>>> > saying,
>>>> > "Rows cannot be programmatically added to the DataGridView's rows
>>>> > collection
>>>> > when the control is data-bound."
>>>> >
>>>> > Am I just not able to add a new record ever if I use a data-bound
>>>> > DataGridView, or do I need to follow some special steps to
>>>> > un-data-bind
>>>> > it,
>>>> > add my data, then re-data-bind it?
>>>>
>>
>

jp2msft

3/14/2008 1:08:00 PM

In my DataTable "Design View" (the .xsd file showing the default
"Fill,GetData()" SQL commands), I created an Insert and an Update SQL command.

Calling them is supposed to return the number of rows affected, but every
time I call them, I get 0 returned.

Can I not just call them outright?

Do I need to set something ahead of time before I call them?

Is there a way to get the reason(s) why the Insert/Update failed? (they are
in a try/catch block, but no error is thrown)

"William Vaughn" wrote:

> Chapter 7 discusses these issues. Start on page 468.
> No, when you have created a DataSet (strongly typed or untyped) and bound it
> to a complex bound control like a DataGridView, once you change the Rows
> collection members (add or delete rows, or change values in existing rows)
> the binding mechanism posts these changes to the bound control. You might
> have to execute EndEdit to get this operation to fire but it's posted
> automatically. You should not have to call "AcceptChanges" in 90% of the
> cases when handling data. AcceptChanges is used to tell ADO that the changes
> marked in the DataTable/DataSet have been processed through independent
> means. If you use the DataAdapter or generated TableAdapter Update method,
> "accept changes" is invoked for you on a row-by-row basis as ADO walks
> through the update process posting client-side changes to the server
> database.
>
> There is an entirely different strategy (that I discuss in the book) that
> ignores the Update method entirely; it assumes that you have stored
> procedures that handle complex updates (multi-table related or cascading
> updates/deletes) without having to use ADO to do the low-level action
> commands for you. This approach uses INSERT SQL to add rows to the database
> and UPDATE and DELETE SQL to change or delete rows. But INSERT does not
> affect the local data store--the local DataTable or TableAdapter
> rowset--only the server-side data store. Keeping these two rowsets in sync
> is the issue. Again, there are several ways to accomplish this including use
> of replication.
>
> You might benefit from my day-long workshop at DevTeach in Toronto on May
> 12th.
>
> hth
> --
> __________________________________________________________________________
> William R. Vaughn
> President and Founder Beta V Corporation
> Author, Mentor, Dad, Grandpa
> Microsoft MVP
> (425) 556-9205 (Pacific time)
> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
> ____________________________________________________________________________________________
> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
> news:AC088AAF-880A-485F-B7F6-B7C81C9A172F@microsoft.com...
> > What page is that described in your book?
> >
> > Is there a cut-and-dry way of showing me how that's done? Your book is
> > great, but 1000 pages just takes me too long to find what I need. (Are you
> > planning a Cookbook in the future?)
> >
> > From what I understand, once the underlying structure has rows added or
> > modified, then I need to create a DataSet of changes made to the main
> > DataSet, updated my TableAdapter with these changes, accept the changes
> > through the main DataSet, then update TableAdapter again.
> >
> > Does all of that sound confusing to you, too?
> >
> > How is all of this better than just creating a new SqlConnection with an
> > INSERT Command? Microsoft did a lot of work with this, but I think it is
> > making things more difficult than they need to be. Is that just me?
> >
> > "William Vaughn" wrote:
> >
> >> Yup, if it's data bound you just add a row to the DataTable (or
> >> structure)
> >> to which it's bound.
> >>
> >> --
> >> __________________________________________________________________________
> >> William R. Vaughn
> >> President and Founder Beta V Corporation
> >> Author, Mentor, Dad, Grandpa
> >> Microsoft MVP
> >> (425) 556-9205 (Pacific time)
> >> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
> >> ____________________________________________________________________________________________
> >> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
> >> news:9E28E7A7-A2D3-4514-BC96-BD2FAD0F1E43@microsoft.com...
> >> >A data-bound DataGridView is wonderfully simple to include with a
> >> >Windows
> >> >Form.
> >> >
> >> > Now that all the data is there, how do I go about adding a new record?
> >> > When
> >> > I tried, Visual Studio 2005 Pro gave me an InvalidOperationException,
> >> > saying,
> >> > "Rows cannot be programmatically added to the DataGridView's rows
> >> > collection
> >> > when the control is data-bound."
> >> >
> >> > Am I just not able to add a new record ever if I use a data-bound
> >> > DataGridView, or do I need to follow some special steps to un-data-bind
> >> > it,
> >> > add my data, then re-data-bind it?
> >>
>

William Vaughn

3/14/2008 3:50:00 PM

This sounds like the Update method was called with no work to do. This is
often caused by calling AcceptChanges or by not calling EndEdit before the
Update (which posts changes from the bound control to the underlying
DataTable).

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
news:B5A8E91B-E7FD-48D2-9E28-BC14873616E5@microsoft.com...
> In my DataTable "Design View" (the .xsd file showing the default
> "Fill,GetData()" SQL commands), I created an Insert and an Update SQL
> command.
>
> Calling them is supposed to return the number of rows affected, but every
> time I call them, I get 0 returned.
>
> Can I not just call them outright?
>
> Do I need to set something ahead of time before I call them?
>
> Is there a way to get the reason(s) why the Insert/Update failed? (they
> are
> in a try/catch block, but no error is thrown)
>
> "William Vaughn" wrote:
>
>> Chapter 7 discusses these issues. Start on page 468.
>> No, when you have created a DataSet (strongly typed or untyped) and bound
>> it
>> to a complex bound control like a DataGridView, once you change the Rows
>> collection members (add or delete rows, or change values in existing
>> rows)
>> the binding mechanism posts these changes to the bound control. You might
>> have to execute EndEdit to get this operation to fire but it's posted
>> automatically. You should not have to call "AcceptChanges" in 90% of the
>> cases when handling data. AcceptChanges is used to tell ADO that the
>> changes
>> marked in the DataTable/DataSet have been processed through independent
>> means. If you use the DataAdapter or generated TableAdapter Update
>> method,
>> "accept changes" is invoked for you on a row-by-row basis as ADO walks
>> through the update process posting client-side changes to the server
>> database.
>>
>> There is an entirely different strategy (that I discuss in the book) that
>> ignores the Update method entirely; it assumes that you have stored
>> procedures that handle complex updates (multi-table related or cascading
>> updates/deletes) without having to use ADO to do the low-level action
>> commands for you. This approach uses INSERT SQL to add rows to the
>> database
>> and UPDATE and DELETE SQL to change or delete rows. But INSERT does not
>> affect the local data store--the local DataTable or TableAdapter
>> rowset--only the server-side data store. Keeping these two rowsets in
>> sync
>> is the issue. Again, there are several ways to accomplish this including
>> use
>> of replication.
>>
>> You might benefit from my day-long workshop at DevTeach in Toronto on May
>> 12th.
>>
>> hth
>> --
>> __________________________________________________________________________
>> William R. Vaughn
>> President and Founder Beta V Corporation
>> Author, Mentor, Dad, Grandpa
>> Microsoft MVP
>> (425) 556-9205 (Pacific time)
>> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
>> ____________________________________________________________________________________________
>> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
>> news:AC088AAF-880A-485F-B7F6-B7C81C9A172F@microsoft.com...
>> > What page is that described in your book?
>> >
>> > Is there a cut-and-dry way of showing me how that's done? Your book is
>> > great, but 1000 pages just takes me too long to find what I need. (Are
>> > you
>> > planning a Cookbook in the future?)
>> >
>> > From what I understand, once the underlying structure has rows added or
>> > modified, then I need to create a DataSet of changes made to the main
>> > DataSet, updated my TableAdapter with these changes, accept the changes
>> > through the main DataSet, then update TableAdapter again.
>> >
>> > Does all of that sound confusing to you, too?
>> >
>> > How is all of this better than just creating a new SqlConnection with
>> > an
>> > INSERT Command? Microsoft did a lot of work with this, but I think it
>> > is
>> > making things more difficult than they need to be. Is that just me?
>> >
>> > "William Vaughn" wrote:
>> >
>> >> Yup, if it's data bound you just add a row to the DataTable (or
>> >> structure)
>> >> to which it's bound.
>> >>
>> >> --
>> >> __________________________________________________________________________
>> >> William R. Vaughn
>> >> President and Founder Beta V Corporation
>> >> Author, Mentor, Dad, Grandpa
>> >> Microsoft MVP
>> >> (425) 556-9205 (Pacific time)
>> >> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
>> >> ____________________________________________________________________________________________
>> >> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
>> >> news:9E28E7A7-A2D3-4514-BC96-BD2FAD0F1E43@microsoft.com...
>> >> >A data-bound DataGridView is wonderfully simple to include with a
>> >> >Windows
>> >> >Form.
>> >> >
>> >> > Now that all the data is there, how do I go about adding a new
>> >> > record?
>> >> > When
>> >> > I tried, Visual Studio 2005 Pro gave me an
>> >> > InvalidOperationException,
>> >> > saying,
>> >> > "Rows cannot be programmatically added to the DataGridView's rows
>> >> > collection
>> >> > when the control is data-bound."
>> >> >
>> >> > Am I just not able to add a new record ever if I use a data-bound
>> >> > DataGridView, or do I need to follow some special steps to
>> >> > un-data-bind
>> >> > it,
>> >> > add my data, then re-data-bind it?
>> >>
>>

jp2msft

3/14/2008 8:51:00 PM

Mr. Vaughn,

Here is what I had to do, that made things work for me. Please correct me if
I did it the "Boneheaded Way":

I created an InsertRecord and a ModifyRecord for my TableAdapter in the .xsd
Designer. When I need to modify or insert a record, I call one of these
methods on the TableAdapter.

Also, I have to select the current row from (or insert a new row into) the
DataSet. With this row, I update my information with the same information
that I used in my TableAdapter.

On the row, I AcceptChanges.

On the TableAdapter, I Update.

This seems to be the only way I've found to ensure that changes that appear
on the screen also persist to my SQL database.

Goodness! I didn't realize I had to save these changes in two (2) places!

Again, if I am doing this completely wrong, or if you can see a smoother way
of accomplishing what I am doing, please let me know.

Regards,
Joe

"William Vaughn" wrote:

> This sounds like the Update method was called with no work to do. This is
> often caused by calling AcceptChanges or by not calling EndEdit before the
> Update (which posts changes from the bound control to the underlying
> DataTable).
>
> --
> __________________________________________________________________________
> William R. Vaughn
> President and Founder Beta V Corporation
> Author, Mentor, Dad, Grandpa
> Microsoft MVP
> (425) 556-9205 (Pacific time)
> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
> ____________________________________________________________________________________________
> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
> news:B5A8E91B-E7FD-48D2-9E28-BC14873616E5@microsoft.com...
> > In my DataTable "Design View" (the .xsd file showing the default
> > "Fill,GetData()" SQL commands), I created an Insert and an Update SQL
> > command.
> >
> > Calling them is supposed to return the number of rows affected, but every
> > time I call them, I get 0 returned.
> >
> > Can I not just call them outright?
> >
> > Do I need to set something ahead of time before I call them?
> >
> > Is there a way to get the reason(s) why the Insert/Update failed? (they
> > are
> > in a try/catch block, but no error is thrown)
> >
> > "William Vaughn" wrote:
> >
> >> Chapter 7 discusses these issues. Start on page 468.
> >> No, when you have created a DataSet (strongly typed or untyped) and bound
> >> it
> >> to a complex bound control like a DataGridView, once you change the Rows
> >> collection members (add or delete rows, or change values in existing
> >> rows)
> >> the binding mechanism posts these changes to the bound control. You might
> >> have to execute EndEdit to get this operation to fire but it's posted
> >> automatically. You should not have to call "AcceptChanges" in 90% of the
> >> cases when handling data. AcceptChanges is used to tell ADO that the
> >> changes
> >> marked in the DataTable/DataSet have been processed through independent
> >> means. If you use the DataAdapter or generated TableAdapter Update
> >> method,
> >> "accept changes" is invoked for you on a row-by-row basis as ADO walks
> >> through the update process posting client-side changes to the server
> >> database.
> >>
> >> There is an entirely different strategy (that I discuss in the book) that
> >> ignores the Update method entirely; it assumes that you have stored
> >> procedures that handle complex updates (multi-table related or cascading
> >> updates/deletes) without having to use ADO to do the low-level action
> >> commands for you. This approach uses INSERT SQL to add rows to the
> >> database
> >> and UPDATE and DELETE SQL to change or delete rows. But INSERT does not
> >> affect the local data store--the local DataTable or TableAdapter
> >> rowset--only the server-side data store. Keeping these two rowsets in
> >> sync
> >> is the issue. Again, there are several ways to accomplish this including
> >> use
> >> of replication.
> >>
> >> You might benefit from my day-long workshop at DevTeach in Toronto on May
> >> 12th.
> >>
> >> hth
> >> --
> >> __________________________________________________________________________
> >> William R. Vaughn
> >> President and Founder Beta V Corporation
> >> Author, Mentor, Dad, Grandpa
> >> Microsoft MVP
> >> (425) 556-9205 (Pacific time)
> >> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
> >> ____________________________________________________________________________________________
> >> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
> >> news:AC088AAF-880A-485F-B7F6-B7C81C9A172F@microsoft.com...
> >> > What page is that described in your book?
> >> >
> >> > Is there a cut-and-dry way of showing me how that's done? Your book is
> >> > great, but 1000 pages just takes me too long to find what I need. (Are
> >> > you
> >> > planning a Cookbook in the future?)
> >> >
> >> > From what I understand, once the underlying structure has rows added or
> >> > modified, then I need to create a DataSet of changes made to the main
> >> > DataSet, updated my TableAdapter with these changes, accept the changes
> >> > through the main DataSet, then update TableAdapter again.
> >> >
> >> > Does all of that sound confusing to you, too?
> >> >
> >> > How is all of this better than just creating a new SqlConnection with
> >> > an
> >> > INSERT Command? Microsoft did a lot of work with this, but I think it
> >> > is
> >> > making things more difficult than they need to be. Is that just me?
> >> >
> >> > "William Vaughn" wrote:
> >> >
> >> >> Yup, if it's data bound you just add a row to the DataTable (or
> >> >> structure)
> >> >> to which it's bound.
> >> >>
> >> >> --
> >> >> __________________________________________________________________________
> >> >> William R. Vaughn
> >> >> President and Founder Beta V Corporation
> >> >> Author, Mentor, Dad, Grandpa
> >> >> Microsoft MVP
> >> >> (425) 556-9205 (Pacific time)
> >> >> Hitchhiker???s Guide to Visual Studio and SQL Server (7th Edition)
> >> >> ____________________________________________________________________________________________
> >> >> "jp2msft" <jp2msft@discussions.microsoft.com> wrote in message
> >> >> news:9E28E7A7-A2D3-4514-BC96-BD2FAD0F1E43@microsoft.com...
> >> >> >A data-bound DataGridView is wonderfully simple to include with a
> >> >> >Windows
> >> >> >Form.
> >> >> >
> >> >> > Now that all the data is there, how do I go about adding a new
> >> >> > record?
> >> >> > When
> >> >> > I tried, Visual Studio 2005 Pro gave me an
> >> >> > InvalidOperationException,
> >> >> > saying,
> >> >> > "Rows cannot be programmatically added to the DataGridView's rows
> >> >> > collection
> >> >> > when the control is data-bound."
> >> >> >
> >> >> > Am I just not able to add a new record ever if I use a data-bound
> >> >> > DataGridView, or do I need to follow some special steps to
> >> >> > un-data-bind
> >> >> > it,
> >> >> > add my data, then re-data-bind it?
> >> >>
> >>
>

Cor Ligthert [MVP]

3/15/2008 12:19:00 PM

JP,

This cannot be the solution because accept changes is to PREVENT that rows
will be updated.

This not for you, because I have seen this written by Bill more times in
this message thread, but for those who because of your answer will have
doubt because of your message in the knowledge of Bill or otherwise take
your solution as true.

Cor

jp2msft

3/17/2008 1:39:00 PM

Thanks Cor,

I'm begining to think now that I should *not* have been working with
DataBound Datasets, but I'm getting pressure to release this so I don't have
time to re-write it.

"Cor Ligthert[MVP]" wrote:

> JP,
>
> This cannot be the solution because accept changes is to PREVENT that rows
> will be updated.
>
> This not for you, because I have seen this written by Bill more times in
> this message thread, but for those who because of your answer will have
> doubt because of your message in the knowledge of Bill or otherwise take
> your solution as true.
>
> Cor
>

Cor Ligthert [MVP]

3/18/2008 5:27:00 AM

You probably need the EndEdit, in fact is that something as "accept the
changes from the DataGridView", but that has Bill as well written before.

Cor

microsoft.public.inetserver.asp.general

胴体国大前屈みナマ升

Nando_uy

William Vaughn

Miro

Miro

jp2msft

William Vaughn

jp2msft

Cor Ligthert [MVP]

jp2msft

Cor Ligthert [MVP]

x Login to ForumsZone