Other alternatives, in my opinion, add complexity without saving appreciable amounts of money.
I'd certainly concur with that - for maximum reliability, keep things as simple as possible. Now that the Vue console is available as a low-cost alternative to the standard VP2 console, users of a Vue or a standard VP2 station have a cost-effective way of getting reception at two distinct local locations.
But this doesn't quite cover all the bases. If you have any supplementary stations (6372/6382/6345) on a VP2 system then a Vue console won't pick these up. And it could be - especially in larger buildings, eg schools, businesses etc - that you can't always get adequate wireless reception at the preferred PC location (ie for the second console).
If you use a serial Weatherlink logger then many different options have been developed over the years for relaying the RS232 data over different wireless and cabled systems. I've looked at quite a few of these over the years (eg device servers to relay the data over a network both cabled and wireless, wireless modems etc etc) and all of them seem to have worked pretty well. Provided the network is purely local then there shouldn't be any significant problems - it's only if you try to move to a wide-area network (ie have some larger distance of several/many miles between console and PC) that timing issues such as latency may start to cause problems.
Choices are a bit more limited with the USB logger but for instance the Silex SX2000 device (I'm sure there are others by different makers) interfaces a USB device to a network. We've had one of these running for a couple of years now, it is capable of both cabled and WiFi network interfacing. We've only had it running in cabled mode but there's no obvious reason why it shouldn't also work perfectly well in wireless mode. In normal routine use this unit has been perfectly reliable and you're simply unaware of its presence, but you do have to remember when powering the system up (eg recovering from a mains outage) that there are extra drivers to be loaded and checked - this is really where the extra complexity comes in and might be a good place to use Softwx's StartWatch to manage the overall startup process.
