R
rt
Hi all,
I've been trying to find some kind of article or white paper explaining the
best practices for linking data to forms or subforms when:
1) You use ADO.
2) You need to display data from at least 3 or 4 or several related tables.
3) Some of the tables are "bridge" or junction tables.
4) The data are pulled in via a recordset, which is then assigned to the
form's recordset property (ex.: Me.Recordset = rstMyData).
5) You are using SQL Server and a client/server solution.
One example might be three tables: "Orders", "Customers", and maybe "Parts",
where the Orders tables may actually be just a bridge table between the
other two, as in a one-to-many and many-to-one relationship. Most articles I
find show a simple two-table / form-subform solution, but do not take into
account more than three updatable related tables in the design. Problems
that come up are how to update more than one table, especially when the
UniqueTable property only gives you access to just one table to update.
Maybe disconnected recordsets would be useful? How do large enterprises
approach a front-end to a database involving dozens of tables? They must use
very efficient methods to get at just the data they need, and reduce the
load on the server, but where to start?
Any ideas on where to look for advanced topics like these? Maybe a book one
of the MVPs have written covering these things? Again, I'm looking for
advanced techniques that can be used within a large enterprise.
Thank you for any insight or information you may have. I love programming in
Access and really want to get to the "bleeding edge" of designing with it!
I've been trying to find some kind of article or white paper explaining the
best practices for linking data to forms or subforms when:
1) You use ADO.
2) You need to display data from at least 3 or 4 or several related tables.
3) Some of the tables are "bridge" or junction tables.
4) The data are pulled in via a recordset, which is then assigned to the
form's recordset property (ex.: Me.Recordset = rstMyData).
5) You are using SQL Server and a client/server solution.
One example might be three tables: "Orders", "Customers", and maybe "Parts",
where the Orders tables may actually be just a bridge table between the
other two, as in a one-to-many and many-to-one relationship. Most articles I
find show a simple two-table / form-subform solution, but do not take into
account more than three updatable related tables in the design. Problems
that come up are how to update more than one table, especially when the
UniqueTable property only gives you access to just one table to update.
Maybe disconnected recordsets would be useful? How do large enterprises
approach a front-end to a database involving dozens of tables? They must use
very efficient methods to get at just the data they need, and reduce the
load on the server, but where to start?
Any ideas on where to look for advanced topics like these? Maybe a book one
of the MVPs have written covering these things? Again, I'm looking for
advanced techniques that can be used within a large enterprise.
Thank you for any insight or information you may have. I love programming in
Access and really want to get to the "bleeding edge" of designing with it!