Michael, VFP is not "all by itself" Client/Server. I do a lot of "remote users" though, through pipes as small as 28.8 modems and the solution *really is* to install your exe on the remote end and have it just access data "back on the server". I wouldn't consider this a "workaround" - it's a very straightforward approach - but it does make it a little bit of a pain in the butt to update your remote executables (since the executable will be in multiple places). There have been some other threads regarding using PCAnywhere, so I won't go into that here (and I'm not an expert on the subject), but regarding RAS - are you thinking of using modems? If you're looking to go ISDN, I would heartily recommend Gandalf ISDN boxes (http://www.gandalf.ca) because they have a fantastic proprietary compression algorithm. You have to use the same box on both ends (I like the 5242i), but I'm seeing 6:1 compression since I'm only passing .dbfs and they compress great - that turns my ISDN into "effectively" half of a T1 - hooha!!! Good Luck, Kevin E. Stroud One of my clients is switching to NT Server, from Netware. Their network consultant asked if VFP is "truly client server based, or just a regular Windows app with SQL capability". He asked because he couldn't decide whether to recommend the client buy 2 gateway PC's running pcANYWHERE to use as dail-up gateway computers - or use the RAS feature in NT - and connect directly (without a gateway). He said the RAS connection would be painfuly slow unless VFP is "truly client server". I called Microsoft and encountered one of their less-than-expert tech support guys who just said to map a drive to the RAS connection and install my EXE on the workstation so only the data goes across the modem line - not the EXE. Since I thought that sounded like a "work around" and not a true solution, I thought I'd ask if anyone can offer some words of experience. Thank you!