You could do that, but it would be a complicated page if you wanted all 
the same functionality as the data view in Access.  It would be simpler if 
you made a page which would let you work with the availability of one 
product at a time rather than the entire list of products and their 
associated availabilities at any time.

Clear Skies


> Hi,

> I am trying to create a page that insert data into my database(the 
d> atabase is located in a remote server), this page is like the data 
access 
p> age in Microsoft Access where when view on the web, you see all the 
r> ecords in that table and you could add, update, or delete the records 
in 
t> hat table. But the question I am having here is: I have a table name 
P> roducts, and it has a relationship a table named Product Availability, 
w> hen you expand one of the records in the Products table, from there you 
c> ould enter info into the Product Availability table, that some of the 
r> elated info from the Products table will cascade into the Product 
A> vailablility table. Is there any why to create a page/form that would 
let 
m> e enter data into the database just like the way I would in the data 
s> heet view?

This can be done. But it's not simple.

For updating multiple records, you can use code like this:
http://www.adopenstatic.com/resources/code/updatemultiplerecords.asp

You'd need to generate the recordset using the Primary Key value of the
parent record.

Cheers
Ken


: > I am trying to create a page that insert data into my database(the
: d> atabase is located in a remote server), this page is like the data
: access
: p> age in Microsoft Access where when view on the web, you see all the
: r> ecords in that table and you could add, update, or delete the records
: in
: t> hat table. But the question I am having here is: I have a table name
: P> roducts, and it has a relationship a table named Product Availability,
: w> hen you expand one of the records in the Products table, from there you
: c> ould enter info into the Product Availability table, that some of the
: r> elated info from the Products table will cascade into the Product
: A> vailablility table. Is there any why to create a page/form that would
: let
: m> e enter data into the database just like the way I would in the data
: s> heet view?