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

This times, sure they'll need some day. By now it can run in an Intranet.
>
>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.


I'm very aware of n-tier design and apps. In VFE I design my apps from a 3 tier approach, due to the framework structure. Since I'll sell that application after I implement it on my customer site and having a full Internet ERP is a plus, I think that my real question is: Are the web development tools, specially web connection ready to develop an ERP?
Should I wait? Stay in 2 tier CS? Use other tools? Is somebody there that has developed a Very Big application using West-Wind and SQL 7?

TIA