Each client will (or should!) have its own unique object by which it references the database, so what better choice for a ClientID?
Fly by Night Consultants<br /> <blockquote><font size="1" face="Verdana, Arial">quote:</font><hr><i>I climbed on the back of a giant albatross<br />which flew through a crack in the cloud<br />to a place where happiness reigned...<br />all year 'round<br />the music played ever so loudly!</i><p><a href="http://thomasfly.com/songs/Traffic/Hole_in_my_Shoe_qt.htm" target="_blank" rel="nofollow">Hole in My Shoe</a><hr></blockquote>
I couldn't agree more with Thomas. At first I had a common RemoteData object for all clients. You cannot imagine how much I was able to simplify my code and how fast some problems got solved when I switched to one client = one RemoteData, and use of this RemoteData as clientID. Stephane
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Lock with ClientID or remoteClient object