>To expand then: I could use a serializable entity object to create the record and serialize it into a local folder. Then I could have a DataManager class to monitor the folder and upload the xml file to the web service. This should be pretty light weight I think. Do you use security on your web service? I was thinking of a method that had two extra parameters for a userid and a password. If they weren't both passed in correct I would just ignore the request. I am not too familar with web service security.

Yes, I have security on the Web Service. However, its methods varies based on its implementation. Some prefer to pass the username and the password at every hit. I prefer to create a cookie, so a Login() method is called at first, and then the user is recognized for all incoming hits. There are also various other mechanisms. When you use a cookie approach, your client need to enable the credentials in order to keep it in memory.