Need advise on back-end process for a form to add vs to update

Hi,
I got a form where user inputs financial information. However, they can come
back and edit the values before the deadline date of submission.

I am designing just one form for input and edit/update for later changes.
The way I am planning to write back-end code is:
If Record exists for this user
Then call update process
Else
Call insert process.

Need advise whether the above approach is appropriate for a asp project.
Thanks.

RE: Need advise on back-end process for a form to add vs to update

I use that process all the time in my ASP pages. There's no reason it
shouldn't work.


"Jack" wrote:

> Hi,
> I got a form where user inputs financial information. However, they can come
> back and edit the values before the deadline date of submission.
>
> I am designing just one form for input and edit/update for later changes.
> The way I am planning to write back-end code is:
> If Record exists for this user
> Then call update process
> Else
> Call insert process.
>
> Need advise whether the above approach is appropriate for a asp project.
> Thanks.

RE: Need advise on back-end process for a form to add vs to update

Thanks for your advise, Beschler. I appreciate it.

"John Beschler" wrote:

> I use that process all the time in my ASP pages. There's no reason it
> shouldn't work.
>
>
> "Jack" wrote:
>
> > Hi,
> > I got a form where user inputs financial information. However, they can come
> > back and edit the values before the deadline date of submission.
> >
> > I am designing just one form for input and edit/update for later changes.
> > The way I am planning to write back-end code is:
> > If Record exists for this user
> > Then call update process
> > Else
> > Call insert process.
> >
> > Need advise whether the above approach is appropriate for a asp project.
> > Thanks.