>A few tips:
>
>Once you DO get your Wed Connection working, make sure to check bridal inheritance to OOPS -proof your brother's (yeah, right!) Marriage License Application. Exiting a marriage is always a painful, even polymorphic experience, which can easily destroy your properties.
>
>Also, throwing rice is no longer recommended by the Audubon Society, because in a small bird consuming said grain it can cause an unfortunate timer event in the middle of the I/O system, leading to a possible fatal exception error.
>
>Other than that, the Wed Connection works perfectly (I hear).
>
>Pertti

Well, I heard that it needs opportunistic locking in order not to let the buffers flush away ... A Refresh() at regular intervals will help, though.
Don't make a SOAP of it, because Wed Connection doesn't allow for .NET via VFP (Visual Foreign Parameter). COM is better, or use a cellphone.
BTW, anyone at version 4 yet ?
I heard CS (Call Service) will be in there.
Now I think of it, I've version 4 on the shelf, named Beta (sorry for the steel), but she's shrink wrapped and that's nothing. Anyway, you could Foreign Transfer Protocol to download her if you want.

Going to WetConnect myself now.