G
Guest
Hi. Wondering if anyone can point me to a document somewhere that might
describe the most elegant way to handle the following scenario:
I will have an ASPX page which will edit a single record in a given table
"MainTable". But within that page the user will be able to select multiple
rows from a scrolling list (ctrl-click). Each row that the user selects will
result in a single row added to a "Map" table which will map the MainTable
row to multiple entries from some other table.
Think of this example: You have a a table called "Person". You have an aspx
page which edits values for one row at a time for each user in the table. But
there's another table called "Artists" and you want to have a scrolling list
of artists from the Artists table on the aspx page for a Person. For each row
in that scrolling list that's selected, a row will be added to yet a third
table called "Map_Person_Artist".
Finally, all of this will be back-ended with SQL Server Stored Proc.s with
no direct-access to the tables.
The question is, is there some document somewhere that describes the most
elegant way to do this kind of thing with ASP.NET and ADO.NET?
Thanks for your help.
Alex
describe the most elegant way to handle the following scenario:
I will have an ASPX page which will edit a single record in a given table
"MainTable". But within that page the user will be able to select multiple
rows from a scrolling list (ctrl-click). Each row that the user selects will
result in a single row added to a "Map" table which will map the MainTable
row to multiple entries from some other table.
Think of this example: You have a a table called "Person". You have an aspx
page which edits values for one row at a time for each user in the table. But
there's another table called "Artists" and you want to have a scrolling list
of artists from the Artists table on the aspx page for a Person. For each row
in that scrolling list that's selected, a row will be added to yet a third
table called "Map_Person_Artist".
Finally, all of this will be back-ended with SQL Server Stored Proc.s with
no direct-access to the tables.
The question is, is there some document somewhere that describes the most
elegant way to do this kind of thing with ASP.NET and ADO.NET?
Thanks for your help.
Alex