Hi, Michael.

If you are worried about initial investment costs and you don't have a solid Linux background, the cheaper option is NT/IIS. Scaling costs depends a lot of the level to which you eventually plan to scale. I saw many cases of Linux implementation that were actually very expensive because good Linux consulting were quite expensive. This is relative, though.

As for the Web Connection issue, just download it and give it a try. Maybe it's not so overrated after all. 8-)

Seriously, I think everyone loves WC because it is really terrific for projects just as yours. The cost and time difference between VFP/WC and VFP/ASP/VB/any other glue can be tenfold or more, even more if you have a good VFP background.



>We intend to deploy an company-wide intranet server. The immediate use is for a particular deparment to view various reports on a set of data. This will require interactive sorting/querying/filtering, and ideally provide some means of securing data from unauthorized use. All of our data is either VFP or Fox2x tables, but would like the option of upscaling to a backend data server.
>
>We are considering IIS/NT vs. Apache/Linux. My boss has experience with the MS solution and can assist with rapid development, but cannot instantly justify the initial investment costs (or scaling costs) We both would like to add the Linux/Apache skills to our knowledge, but have no idea how well we can interface with our foxpro data.
>
>In the VFP community, it is almost a knee-jerk reaction to point anyone asking about foxpro and web access to the www.west-wind.com site. I am hoping to get more in-depth information about these options...