Subforms instead of Views

[GREABR]

I was looking through posts regarding Views, Stored Procedured, Unique Table Propery, etc., very common that one would like to update more than one table using a form like is possible using a query in .mdb.

Mostly I saw solutions using stored procedures as the recordsource or Forms using unbound fields and updating with code.

Is is possible/acceptable to use only subforms for the related fields where the form uses a table (not a view or stored procedure) and the subforms use the (could be more than one) related tables as recordsources.

Ideas, Pros/Cons, please.

"Don't be afraid to do things wrong, before you do them right"
Bradley Greaves

 

[cmmrfrds]

One table can be updated in an sql server update statement. You could use a subform for each table that is related to the Main table i.e Parent to multiple Child tables.

 

[GREABR]

Can it work so that, for the Form and Subforms - the adds and edits are syncronized and appear seamless. Then I assume that deletes would cascade automatically. Is somenthing like this possible/reasonable?

"Don't be afraid to do things wrong, before you do them right"
Bradley Greaves

 

[cmmrfrds]

The relationships are handled by sql server. So, if you want cascade deletes then set it up that way on sql server.