What access method should I use?

[Steve]

As you will gather I am new to FoxPro 8 and would just like some
general direction.

I have a client that is going to use FoxPro 8, upgrading from FoxPro 1
or 2... They are handling all the conversions/rewriting of the
program. They have a main office with about 8 users and 4 off-site
offices with 3-4 users. They also have people that will work from
home and from customer sites when traveling.

I am setting up a new network from the ground up, Internet access
etc... most likely using DSL at all locations.

I need to be able to access FoxPro, and exchange and data.

My question is:

1) Is SBS2003 a fit for this? From the FoxPro side! I know a can VPN
in and get to email and data or use OWA.

2) Or should I be using 2 servers and access FoxPro from a web server?

FoxPro is the most important application here, the correct access for
this will drive the network configuration. Any suggestions will be
greatly appreciated.

[Eric den Doop]

Hello, Steve!
You wrote on 20 Aug 2004 11:15:43 -0700:

S> I am setting up a new network from the ground up, Internet access
S> etc... most likely using DSL at all locations.
S> I need to be able to access FoxPro, and exchange and data.
S> 1) Is SBS2003 a fit for this? From the FoxPro side! I know a can VPN
S> in and get to email and data or use OWA.
S> 2) Or should I be using 2 servers and access FoxPro from a web server?

I'd go for a single database and a Terminal Service (Remote Desktop)
connection. This way, you can keep both software and data on a single
location. The people on the LAN can access the app over the local network,
while remote users log on to there remote desktop thru RDP. Of all different
solutions I've worked on, some with difficult synchronization tools, some
with web services, RDPing over Citrix or TS has been the easiest and
cheapest solution.

[Steve]

Post by Eric den Doop
I'd go for a single database and a Terminal Service (Remote Desktop)
connection. This way, you can keep both software and data on a single
location. The people on the LAN can access the app over the local network,
while remote users log on to there remote desktop thru RDP.

This sounds fine for the main office users ... But how would the
remote locations get access to the VFP8?

Also I just learned that I will NOT need SBS as they are happy with
the Internet email solution they have.

So, if I am not mistaken you cannot setup a standalone terminal server
without having a domain? Which TS appears to be the best solution to
this and the preferred way to do this type of setup would be with a
domain controller and a TS server ... Right?

Steve

[Eric den Doop]

Hello, Steve!
You wrote on 23 Aug 2004 07:28:13 -0700:

S> This sounds fine for the main office users ... But how would the
S> remote locations get access to the VFP8?

No problem. They can use a VPN connection to connect to the TS or connect to
the TS directly over the internet, but there are safety issues that a sys
admin may not like about this option. I sometimes connect to our TS over 9.6
kb GSM. While it is slow, it's still OK to open up my Outlook and read my
mail. If you have a faster connection, then I don't see a problem working
with VFP or a VFP app on a remote desktop.

S> So, if I am not mistaken you cannot setup a standalone terminal server
S> without having a domain? Which TS appears to be the best solution to
S> this and the preferred way to do this type of setup would be with a
S> domain controller and a TS server ... Right?

I believe you can setup a TS without having a Windows domain. But imagine if
you can't, then what's the problem with setting up a small domain just for
the TS? I've been using Windows 2000 and Windows 2003 Terminal Servers for
years and it's one of the Windows features I like most.

[François 37]

by default TS connections are encrypted and TS 2003 even support file
tranfers

Post by Eric den Doop
Hello, Steve!
S> This sounds fine for the main office users ... But how would the
S> remote locations get access to the VFP8?
No problem. They can use a VPN connection to connect to the TS or connect to
the TS directly over the internet, but there are safety issues that a sys
admin may not like about this option. I sometimes connect to our TS over 9.6
kb GSM. While it is slow, it's still OK to open up my Outlook and read my
mail. If you have a faster connection, then I don't see a problem working
with VFP or a VFP app on a remote desktop.
S> So, if I am not mistaken you cannot setup a standalone terminal server
S> without having a domain? Which TS appears to be the best solution to
S> this and the preferred way to do this type of setup would be with a
S> domain controller and a TS server ... Right?
I believe you can setup a TS without having a Windows domain. But imagine if
you can't, then what's the problem with setting up a small domain just for
the TS? I've been using Windows 2000 and Windows 2003 Terminal Servers for
years and it's one of the Windows features I like most.
--
Eric den Doop
www.foxite.com - The Home Of The Visual FoxPro Experts - Powered By VFP8