To All,
Just a guideline on the best practice for this issue.
I have a number of tables in SQL, and I want to join across them and display
their corresponding values in a datagrid. For example (fictitious), I have a
username, and they have a country associated with them. I join User to
Country (on CountryId) and want to display CountryName in the gridview. In an
ideal world we would still be able to edit/save the gridview without having
to go into a details view of the row.
So, at the moment the suggested solutions are to either handle this in the
OnRowCreated event on the gridview, and manually bind it here.. or create a
custom sproc that simply does the joins for you - and use
AutoGenerateCol umns=True. Personally I am not a fan of either. My original
suggestion up front would be to leverage Linq to Sql, but this was shot down
by the old schoolers here.
Regards
Just a guideline on the best practice for this issue.
I have a number of tables in SQL, and I want to join across them and display
their corresponding values in a datagrid. For example (fictitious), I have a
username, and they have a country associated with them. I join User to
Country (on CountryId) and want to display CountryName in the gridview. In an
ideal world we would still be able to edit/save the gridview without having
to go into a details view of the row.
So, at the moment the suggested solutions are to either handle this in the
OnRowCreated event on the gridview, and manually bind it here.. or create a
custom sproc that simply does the joins for you - and use
AutoGenerateCol umns=True. Personally I am not a fan of either. My original
suggestion up front would be to leverage Linq to Sql, but this was shot down
by the old schoolers here.
Regards
Comment