Ladies and gentlemen: I am building a project management system for a large insurance company. In the requirements is a comprehensive project information form that is divided into 10 sections. We have chosen to implement that as a single ASPX page with 10 panels, each hosting a user control with the server controls representing the form fields within that section. This will keep us from calling the database every time the user changes pages.
In terms of Data Architecture, we have been following the model set forth in the IBuySpy portal. It has worked well for us. However, we had thought that this page would be better supported by a single strongly typed dataset. Our design concept is that the dataset would be filled on page load, then the user components would bind their controls as needed. If a user changes a value, validation occurs and the dataset is updated. On clicking the page- level Submit button, the dataset will update the database. My problems are with programability, reliability and Microsoft's marketing department. Is this as simple as it sounds? Does a strongly typed dataset respond well when there are 9 tables in the dataset and 400 users pounding on it? Is this, in essence, another RDS - a 'one size fits all' solution that doesn't really work (at least at the enterprise lever)? I would appreciate feedback from the joint conscience. I'm quite strong at some levels of .Net, but enterprise ADO can be tricky. Thanks in advance for your thoughts. -- William A. Sempf MCP, CIBS, CIW Paros Business Partners Senior Consultant Author of Effective Visual Studio.Net (Wrox Press) You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
