Thomas,
I gotta agree, thats damn good advice!
The route I ended up going with my current project is VID to design the front end screens, WebConnect to execute FoxScript and handle client specific business rules and COM CodeBook framework to data integrity rules and the data tier.
So far so good.

Thanks for your reply

Chris






>Christopher;
>
>Visual Interdev is not my favorite development tool. It might be the best available for ASP though. The concept of the Design/Soruce/QuickView screens is interesting, but like many Microsoft products does not work as expected. When you are creating ASP, QuickView is not usable - you have to switch to the browser. Design mode is O.K. as long as you do not reference any object to an ADO object/field. That makes Design mode unavailable.
>
>The forms I am creating (this is a corporate project - I suggested West Wind Connection and was told no) will have at least 3000 lines of code each, an average of nine tables per page, and at least six Include files per page. There are dozens of forms. There is no joy in what I am doing but the people in charge realize I am breaking new ground and happy with my accomplishments. It will take months to get this application completed. Then someone will say, how about adding a text box to that form? I get paid to suffer - what more can I say?
>
>I indent my code for readibility and VI reformats what ever it wants and how it wants it. After perhaps a dozen times of fighting the formating changes, VI has allowed me to have things my way. Take my work for it - VI is more than a text editor, but not much more.
>
>My advice using VI:
>1. Do not use any drop on controls! Reliability is an issue here.
>2. Write all lines of code yourself.
>3. Do not create a VI project for your site. I write all my ASP pages as free pages and put them in the required directory.
>4. Do not use it as suggested to deploy your web site.
>5. Expect your project to take longer than any VB/VFP project you have ever worked on.
>6. Your feature set should not be too complex unless you have a lot of time to burn.
>7. When your form begins to get "large" only add one object/feature at a time and test it to be sure everything still works. The debugger only works to a point.
>8. Take up a hobby not related to application development.
>
>People are suprised at what my application is able to accomplish. It is for a corporate Intranet and runs fast. It has the look and feel of a client/server application on a Lan. Oh well, in a few months I should have version 1.0 rolled out.
>
>My take on web development with these tools is it is not ready for prime time. If this was the military and the application mission critical, we would be dead.
>
>Tom