<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<div>If you are willing to move to linux I know someone who can help you.</div><div>Contact me at linda@Grayranch.us </div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:88%;color:#364f67" dir="auto">Sent from my Verizon 4G LTE smartphone</div></div><br><br>-------- Original message --------<br>From: Robert Haussmann via Filepro-list <filepro-list@lists.celestial.com> <br>Date: 11/9/16 4:11 PM (GMT-05:00) <br>To: Filepro List <filepro-list@celestial.com> <br>Subject: RE: Hosting filePro off-site <br><br>Del--I can recommend Georgia Softworks telnet server for Windows for situations like this (Windows environment). This could be done either directly, or over VPN (I recommend the latter for security purposes). Your clients would run either the Georgia Softworks telnet/SSH client (or any telnet/SSH client actually) and it's as if you were telnetting/SSHing into a *nix server (based on my limited knowledge here). The filePro executables all run on the server, so the only thing going "over the wire" are keystrokes/screen display.<br><br>Not sure about printing in such a setup--we do this all locally (with the printers defined on the server as networked printers). I would imagine that you could use site-to-site VPN to create a similar setup (defining printers, if they are networked, on the client side such that the server can see them over the site to site connection).<br><br>Bob<br><br>-----Original Message-----<br>From: Filepro-list [mailto:filepro-list-bounces+haussma=nextdimension.net@lists.celestial.com] On Behalf Of Fairlight via Filepro-list<br>Sent: Wednesday, November 09, 2016 2:38 PM<br>To: filepro-list@lists.celestial.com<br>Subject: Re: Hosting filePro off-site<br><br>On Wed, Nov 09, 2016 at 02:24:58PM -0500, Scott Walker via Filepro-list thus spoke:<br>> <br>> I've never been a fan of fp running on a Windows server and I don't <br>> know much about it, either locally or on a hosted server. Just that <br>> it has always been way slower on a local server so I would expect that <br>> to be the same on a hosted Windows server.<br><br>I wasn't going to dive into it, but there are a few options...<br><br>1) Actual native filePro over a VPN, in which case all your index/key data which would normally be read on the LAN will go over the WAN via the VPN.<br>This will impact speed; the degree to which it alters the speed depends upon the network bandwidth available. However, in cases where you may be reading a whole 2GB (or more in 5.6+) file -plus- index data in order to run a full report are going to be painful even on 300mbit connections. Not recommended.<br><br>2) RDP of some sort. I personally find RDP to be a very inefficient way to work, and even the best RDP software out there is prone to occasional redraw issues. I don't recommend this for anything but casual or periodic-of-necessity work.<br><br>There is no way I can see of working remotely on native Windows filePro which is actually ideal. I would never recommend it being adopted as the primary model. RDP once in a while is fine, but as the mainstay, no.<br><br>mark-><br>--<br>Audio panton, cogito singularis.<br>_______________________________________________<br>Filepro-list mailing list<br>Filepro-list@lists.celestial.com<br>Subscribe/Unsubscribe/Subscription Changes http://mailman.celestial.com/mailman/listinfo/filepro-list<br>_______________________________________________<br>Filepro-list mailing list<br>Filepro-list@lists.celestial.com<br>Subscribe/Unsubscribe/Subscription Changes<br>http://mailman.celestial.com/mailman/listinfo/filepro-list<br><br></body></html>