Is there a way to have a page on my website where our users can create
and invoce by filling in the blanks and then have it print out
complete but save the information in a text file to be added to a
database later?

Do I just use a form and have it save the info as a comma delimited text
that I can import into access?

Do I setup the submit button so that the confirmation page its the completed
invoice and that will allow them to print it?

Also what is the easiest and safest way to password that page so no
one from the outside who stumbles accross it can fill out invoices? I
am not plaing it as a menu choice on our website but you never know if
someone hits some wrong keystrokes and the next thing you know they are
on that page.

Thanks

Hi Dig,

I hope you like to tinker.

> Is there a way to have a page on my website where our users can create
> and invoce by filling in the blanks and then have it print out
> complete but save the information in a text file to be added to a
> database later?
>...
> Also what is the easiest and safest way to password that page so no
> one from the outside who stumbles accross it can fill out invoices? I
> am not plaing it as a menu choice on our website but you never know if
> someone hits some wrong keystrokes and the next thing you know they are
> on that page.

The first thing you need to understand is that what you've described with
your questions above are the requirements for a web application. The
difference between a "static" web and a web application is that a static web
is just a bunch of HTML documents. You can read them, and that's about it. A
static web may have a couple of forms, such as a Feedback form, a few active
components such as a Hit Counter, etc., but it is in essence simply a
collection of documents that are only related (perhaps) in terms of subject
matter.

A web application is a set of web pages which respond to user input and are
related by a "work flow." That is, there is a sequence of processes that
proceeds from one to the next, and the web application, comprised of the
various server-side components and client-side web page interfaces,
coordinates all of these together.

Let's have a look at the work flow you've described:

1.Password entry to the functionality incorporated in the application.
2. A means of creating documents (invoices) and storing data about these on
the server.
3. A means of printing these documents.

Admittedly, it's not a big application, but as you can see, there is a
sequence to it, and a relationship between all of the elements involved.

The reason I started with this is to first, get you thinking about this in
the right way, and second, to illustrate to you that this is basically a
custom web application, not just something you can get "out of a can." It
will require you to wire the whole thing together.

But take heart: Big things are made up of lots of little things (as my Uncle
Chutney sez), and your "big thing" isn't really very big at all. There are
only 3 (or 4, if you split number 2 into its compoenent parts) parts to it.
All you need to do is learn enough to do each of the 3 parts separately and
then "wire them together."

I've compiled a short list of resources that will help you in this endeavor:

Password-Protecting Web Pages with ASP:
http://blogs.msdn.com/lisawoll/archi...24/432429.aspx


Using FrontPage for ASP and Databases:
http://msdn.microsoft.com/office/und...p/default.aspx


Using CSS for Printing Layout:
http://www.alistapart.com/articles/goingtoprint/

FrontPage Technical Articles (General):
http://msdn.microsoft.com/office/und...fault.aspx#asp

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Show me your certification without works,
and I'll show my certification
*by* my works.