Hello,
I am currently declaring my select/insert/delete/update in the aspx form (using SqlDataSource), but have come to realise that a better implementation would be to use ObjectDataSource and a 3-tier architecture rather than SqlDataSource. Therefore, I have followed the method described in RadScheduler: Getting Started. However, I don't understand how the appointments are persisted using this method?
I'd like to build on the code in the Getting Started article to persist appointments in an SQL Server database.
Please can you advise how to go about doing this outlining the types of data sources that I should use as I'm a bit lost with where to go from here?
Regards,
Anthony
I am currently declaring my select/insert/delete/update in the aspx form (using SqlDataSource), but have come to realise that a better implementation would be to use ObjectDataSource and a 3-tier architecture rather than SqlDataSource. Therefore, I have followed the method described in RadScheduler: Getting Started. However, I don't understand how the appointments are persisted using this method?
I'd like to build on the code in the Getting Started article to persist appointments in an SQL Server database.
Please can you advise how to go about doing this outlining the types of data sources that I should use as I'm a bit lost with where to go from here?
Regards,
Anthony
1 Answer, 1 is accepted
0
Anthony
Top achievements
Rank 1
Rank 1
answered on 12 Aug 2010, 03:01 PM
Cannot delete the original post, so ignore.