Isn't it simplier to just do like when you purchase something? You also
need a prove then that you have paid and are expecting the merchandise
to be shipped. That is simply solved with mailing a copy plus a
registration number for future reference.
Should be more than enough.
--
Maxim Maletsky
Hi Bryan
Thanks for the suggestions.
Can you elaborate on the pdf option? Wouldn't that mean the users would
need a copy of adobe acrobat writer?
On Tue, 2003-01-28 at 21:53, Bryan Brannigan wrote:
3 choices as I see it..
a) create a PDF for download
b) let the users create the form in
I have a rather annoying problem regarding forms.
I have built an app that allows the users to fill in a rather large form
(much like a claim form) and then have the data pumped into a mysql db.
The problem is: the users want to be able to save their forms on their
systems as a) backup/proof
--- Petre Agenbag [EMAIL PROTECTED] wrote:
I have a rather annoying problem regarding forms.
I have built an app that allows the users to fill
in a rather large form (much like a claim form)
and then have the data pumped into a mysql db.
The problem is: the users want to be able to
save
Hi Chris
On Tue, 2003-01-28 at 22:09, Chris Shiflett wrote:
--- Petre Agenbag [EMAIL PROTECTED] wrote:
I have a rather annoying problem regarding forms.
I have built an app that allows the users to fill
in a rather large form (much like a claim form)
and then have the data pumped into a
--- Petre Agenbag [EMAIL PROTECTED] wrote:
This is exactly what I'm looking to do; but my problem
remains: I don't know what the best solution is. The
problem is clear: the users actually need an electronic
copy of the data they submit; they must revisit certain
issues annually, and would
On Tue, 2003-01-28 at 22:09, Chris Shiflett wrote:
--- Petre Agenbag [EMAIL PROTECTED] wrote:
I have a rather annoying problem regarding forms.
I have built an app that allows the users to fill
in a rather large form (much like a claim form)
and then have the data pumped into a
(for printing off)
or copying to another form which could be used for next years data
Regards
Adam White
-Original Message-
From: Petre Agenbag [mailto:[EMAIL PROTECTED]]
Sent: 28 January 2003 20:17
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP] best way to save form data
On Wednesday 29 January 2003 04:17, Petre Agenbag wrote:
save their forms on their systems as a)
backup/proof that they have filled it in and b)
for their records for future use and c) the hope
is that it would also allow for a reliable method
to complete the form off-line and then
]
za cc: [EMAIL PROTECTED]
Subject: Re: [PHP] best way to save
form data on user side
on 29/01/03 6:35 AM, Petre Agenbag ([EMAIL PROTECTED]) wrote:
Hi
I have a rather annoying problem regarding forms.
I have built an app that allows the users to fill in a rather large form
(much like a claim form) and then have the data pumped into a mysql db.
The problem is: the users want
You could use the mail() function to automatically send an email to your
user. In the email could be an html page with the same form they'd filled
out plus some hidden input fields which would tell you that they are
updating their stored information. With this, your user gets confirmation
of
12 matches
Mail list logo
