Hi There,
not up to speed with online forms etc but my first instinct would be if the database is already open, then isn't it locked for other entries until the table is closed?
an idea would be to have the info from the asp pooled for a mass update and then have the info collected updated periodically to the table.
it could i guess, be pooled in vb state with unique ids to prevent errors then the code could write to the table at set intervals then clear the code.
like i say, im not familiar with online stuff but that would be the route i would look at if i was faced with this scenario.
NS