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
[
on
of what was submitted, a way to edit their initial input and a record which
they can keep on their own computer.
Hope this helps,
Hugh
- Original Message -
From: "Petre Agenbag" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 28, 2003 11:35 AM
Subj
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 wa
AIL PROTECTED]
za> cc: [EMAIL PROTECTED]
Subject: Re: [PHP] best way to save
form d
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 o
page (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 da
> 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 pu
--- 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 wou
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 pum
--- 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
> "
> 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/
reate the form in Excel and then figure out a way to
> import that into your database using a webapp
> c) client side app :(
>
> > -Original Message-
> > From: Petre Agenbag [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, January 28, 2003 2:35 PM
> > To: [EM
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 to be able to "save" their forms on their
systems as a) backup/proof
13 matches
Mail list logo
