Is it Access Control? Help Please

[Ted Wilson]

I have a Table with 4 columms on Access and I am using ASP to insert records.
(UserID) (Email)(Product)(Colour). I use a Form and a Command page to insert
UserID and Email. After that another page is loaded user enters Product and
Colour choice. Now the Product and Colour data is inserted on another row
from below UserID and Email row. How can I stop the record input jumping to
another row and complete record on the same row as UserID and Email
previously inserted. Is it done on ASP?

Thanx

 

[Dirk Goldgar]

I have a Table with 4 columms on Access and I am using ASP to insert
records. (UserID) (Email)(Product)(Colour). I use a Form and a
Command page to insert UserID and Email. After that another page is
loaded user enters Product and Colour choice. Now the Product and
Colour data is inserted on another row from below UserID and Email
row. How can I stop the record input jumping to another row and
complete record on the same row as UserID and Email previously
inserted. Is it done on ASP?

This would actually be completely outside the control of Access itself.
If your VBScript code inserts a record in the database on one page, and
then inserts a record (with different information) in the database on
another page, you're going to have two records in your database. What
you need to do, in vague terms, is either (a) don't add a record at all
until you have collected all the information you want to save in it --
UserID, Email, Product, and Colour -- or (b) insert the record from one
page, get the primary key of the record you just added, pass it to the
second page, and let the code on that page update that record rather
than inserting a new one. The exact details of how to implement
whichever approach you choose depend on the specifics of your ASP
application.