Hi Harold, How about gathering all of the data for both tables on one page ... and sorting out the inserts on the backend? That would also give you a 'cleaner' design for bouncing partial data - say from a user that only gives you the update info for table 'a', and insufficient data to update table 'b'. HTH, RonL. -----Original Message----- From: Harold Maduro [mailto:harold at bootstudio.com] I got an ASP page where i input some data into a table in Access Database (let's call this, TABLE A). After this is done, i want to redirect the user to a page to input more data on another table (TABLE B) that has a relationship with TABLE A..