>It's time to do it again...
>I have a contract to build an enterprise system again. Everything:
> GL, Purchases, Payrroll, Logistics, etc. Also, I have a year to do it. It should be SQL Server 7.0 based, about 150 users. Currently I'm using VFE 6.0. I'm thinking about going to the Web. Should I do it in Web Connection? Or the monolithic C/S approach I'm using now is neccesary?
>

This depends heavily on your requirements. Will the client need access from the web? If not, why bother?

But there are some good design methodologies that you can follow to help you easily move your application to the web if the client ever wants it. They involve encapsulating your business logic and data access into business object classes, and making sure that your program only accesses the data through these objects. This is called a 3-tier design, and it ensures that when the time comes to switch interfaces (from VFP to web), you don't have to rebuild your business logic. There are a bunch of articles and samples for programming this way, you can search here for "n-tier" and check out Jim Booth's article on n-tier design on his web site.