Hi folks,
Lots of questions below. Thanks in advance for your help!
1. I go into the query expression builder, I show a lot (like 20 or 30)
tables and queries, I create inner joins and left joins and so on, and build
what winds up looking like a very complicated-looking QEB layout. I have
been very deliberate and careful about structuring the tables and queries in
the upper portion of the QEB so that it's easy to see how they all join and
relate to one another. I test the results, everything's working fine, I
close the QEB. A few minutes later I decide I need to add one more field,
so I open the query again. Then I look at the upper portion, and I cringe in
horror at the tangled, unstructured mess of tables and queries layed out in
in seemingly random order. Is there any way to make the QEB "remember" the
latest layout, instead of presenting me with a garbeled mess? I suspect
there is not, because all it's storing is the SQL. Any ideas? I hate having
to spend minutes dragging and moving tables every time I open a complicated
query.
2. I have a few (like 3 or 4) well-designed tables (ie. they've got primary
keys, relationships, normalized). One of the tables has a lot (like over
100,000) records. I want to build a form that allows the user to view and
edit data after drilling down to the dozen or so he's interested in. Now, in
general, I think there are a lot of different ways to achieve this. I can
create one main form that contains subforms inside subforms, and use Child
and Master links to keep them all synchronized. I've found that this
approach works, but it really drags, it responds very slowly. Another
approach is to use subforms without Child and Master links, and instead use
a function as criterea inside each subform's recordsource, where the
function assignment is tied to a field on the master form. This is similar
to using master/child links, but seems to be quicker for some reason. The
problem with it is that I have to code lots of .Requeries in VBA to update
all the downstream subforms. Any opinions on what the fastest approach is?
My goal is for the end user to get fast-as-possible response when he's
drilling down to the data he wants.
OK, more later.
Gary
Lots of questions below. Thanks in advance for your help!
1. I go into the query expression builder, I show a lot (like 20 or 30)
tables and queries, I create inner joins and left joins and so on, and build
what winds up looking like a very complicated-looking QEB layout. I have
been very deliberate and careful about structuring the tables and queries in
the upper portion of the QEB so that it's easy to see how they all join and
relate to one another. I test the results, everything's working fine, I
close the QEB. A few minutes later I decide I need to add one more field,
so I open the query again. Then I look at the upper portion, and I cringe in
horror at the tangled, unstructured mess of tables and queries layed out in
in seemingly random order. Is there any way to make the QEB "remember" the
latest layout, instead of presenting me with a garbeled mess? I suspect
there is not, because all it's storing is the SQL. Any ideas? I hate having
to spend minutes dragging and moving tables every time I open a complicated
query.
2. I have a few (like 3 or 4) well-designed tables (ie. they've got primary
keys, relationships, normalized). One of the tables has a lot (like over
100,000) records. I want to build a form that allows the user to view and
edit data after drilling down to the dozen or so he's interested in. Now, in
general, I think there are a lot of different ways to achieve this. I can
create one main form that contains subforms inside subforms, and use Child
and Master links to keep them all synchronized. I've found that this
approach works, but it really drags, it responds very slowly. Another
approach is to use subforms without Child and Master links, and instead use
a function as criterea inside each subform's recordsource, where the
function assignment is tied to a field on the master form. This is similar
to using master/child links, but seems to be quicker for some reason. The
problem with it is that I have to code lots of .Requeries in VBA to update
all the downstream subforms. Any opinions on what the fastest approach is?
My goal is for the end user to get fast-as-possible response when he's
drilling down to the data he wants.
OK, more later.
Gary
Comment