I wouldn't imagine much of a problem for 40 connections. I wasn't actually
suggesting connecting to the Web service at all, however, but directly to
SQL Server. It shouldn't have any problems handling 40 connections...
Paul T.
In this architecture there really wouldn't even be a local SDF database at
all then. Just direct communication with the SQL Server database via wifi
eh?
Guess you'd want to make transactional updates? case user interupts the
save or something?
Thanks
Harry
>I wouldn't imagine much of a problem for 40 connections. I wasn't actually
>suggesting connecting to the Web service at all, however, but directly to
[quoted text clipped - 36 lines]
>>>> TIA
>>>> Harry
Paul G. Tobey [eMVP] - 21 Aug 2007 17:03 GMT
Yes, that's what I'm talking about. If you have multiple updates that must
all be done or none of them be done, yes, you'd need to transact. You'd
probably use transactions anyway, for that matter. If you got a cancel
indication from the UI while you were in the middle of some long update, you
should be able to abort the transaction.
Paul T.
> In this architecture there really wouldn't even be a local SDF database at
> all then. Just direct communication with the SQL Server database via wifi
[quoted text clipped - 46 lines]
>>>>> TIA
>>>>> Harry