This turned out to have nothing to do with the ServicedComponent configuration.
I believe it was a DataSet issue. My code was creating and populating my entire DataSet (several tables, related together) before calling the 1st DAL method when I used a single BusinessComponent method. When I changed to use multiple BusinessComponent methods, I also moved the DataSet population code to the BusinessComponent methods. Basically, what I realize is that if I populate a table in the DataSet, then update the RDBMS from the DataSet, populate another table (including a relation back to the 1st table) and update the RDBMS from the DataSet, everything flowed as expected. Thanks to SQL Profiler for showing me that the Sprocs were not doing anything in one case, but were doing lots of (good) things in the other. Howard =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
