>>
>>You can use an overload on your calls in your business object that accepts a command type. Also you can set the default at each business object different if you wish. There is lots of flexibility in that.
>>Tim
>
>
>I could, but I have a *lot* of business objects and don't want to have to overload each instance. I'm wary of the side-effect of changing the default CommandType, but I reckon I could try that and see what breaks.
>
>Eric

Hi Eric,

sorry for the delayed response as I was away for a few days. The CommandType is a property and can be set at the application base business object level, the individual business object level or directly when you make a method call which supports that. There is no overloading. By using the overload method and setting the commandType then would not break anything as the method call includes either a stored procedure or a SQL pass through. Setting the property at the business object is just a convenience so you don't have to specify the command type at each method.
Tim