I am doing web development here. We are not using WC for our web development, but what I can suggest is that you make sure your bizobj's are not in the same classlibs as UI stuff. Also make sure there are no UI calls in any of you bizobj's. Also make sure your classes are logically organized before compiling the dll's to avoid dll hell.

I've been having a great time converting cursors to ADO and sending that to ASP pages. (It's a snap with MM.) When it's time for an update, it's a pretty straight forward process: the client calls the server object's update method with the chnages as parameters, and the data gets updated. (We are using a VFP backend for now.) This is only one approach. SQL Server 2000 has native xml support, and that is probably a better way to go, given that xml is quickly becomming the standard for data transport platforms.

Another suggestion I have would be to wait. Kevin will be releasing a new version shortly, and it's guaranteed to have a lot more support for exactly what you are trying to achieve. By the time you get a good start on Step 2, the new framework will probably clear up a lot of questions for you.

Regards,

Jim