Our client has a website, where he offers the ability for his customers to fill in one of 4 forms, to create an online Order or an online Quote. Both of these forms when completed are turned into emails and emailed to his staff in various locations.
However, they have now determined that each of these forms, will require DIFFERENT validations, depending on whether the form is an ORDER or a QUOTE.
Your job will be to take each of these 4 forms, and create 2 different ones each (to total 8 forms when done). For instance the [url removed, login to view] form, will have to be turned into an [url removed, login to view] form and a [url removed, login to view] form. The ORDER form for each, will be the same validation wise; it is the new QUOTE form that will have different validations needed.
This task will entail NO redesign of the html etc. that controls the look/feel of the page at all, just the duplication of each, renaming of each and then crafting the new validations for the new QUOTE forms.
The new QUOTE form validations will be sent to me by the client later today, and I will post them here as a simple .txt file, but the expected changes will be not very big.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
In an ASP environment, ie w2k/w2k3 server....