Where in the Code can I Call a function Before Insert

Question

Hi, using DWMX and VBSCRIPT with n MS Access table set on a
W2k3 server and ASP
I need to insert a value 'intGradID' from a function into a
hidden field 'hGradID' when the submit button (to insert a record
in an access database) is clicked (and before insert takes place as
this is the key field that I am adding).
I realise Javascript might be required (not too great with
Java) so any help please tell me where to put script/code and what
to put. Thanks.

Answer 1

Why not just setup the field in the record to be
auto-incrementing? That way
on insert the next # in the series is assigned to the new
record. And even
if 2 people someone did it at exactly the same time, the
server takes care
of the collision.
"Dave(UK)" <[email protected]> wrote in
message
news:e9uakp$s11$[email protected]..
> Hi, using DWMX and VBSCRIPT on a W2k3 server and ASP
>
> I have an on-line application form for Graduates (bound
to Insert Into a
> table
> called graduates). On open of the page (at the top) I
have some some code
> to go
> look in the Graduates table for the last gradID No and
add 1 for this new
> Graduate and I set a session variab;e with the GradID
found and that value
> is
> the 'Initial Value' of a hidden field hGradID which is
inserted into
> GradID in
> the table on Submit, along with the other info. Works
Perfectly!! Until,
> that
> is, during the course of one Graduate registering,
another tries to do so
> ..
> both get the same gradID and the one who submits last
ends up with the
> error
> 'Dulicate in Key field '(ie GradID in the table). What I
got to work was
> to set
> up another table (GradOn) into which at the end of the
GradID+1 routine,
> the
> GradID was entered and when the form was submitted, it
ran a routine to
> delete
> the contents of GradOn. Then if the form was opened
again by another user,
> the
> first routine now was to check for a presence of a
record (any record) in
> the
> GradOn Table - if a record existed, it redirected to a
'Registration in
> Progress - Please try later page' ... again all worked
well, perfectly,
> until
> a. The user left the form open for hours
> b. The user used the browser to wuit the page instead of
the logoff which
> ran
> a routine to 'Delele * from GradOn'