E
efandango
Hi Graham,
well... it's a bit complex, but...
The form is a subform called frm_Links and is on its own tab page and is
linked to the main form (frm_Runs) using master/child [Run_No] for both
settings.
On this form are two other forms. frm_Link_Waypoints and
frm_Road_Restrictions_Links. The first one is linked to frm_Links using
master/child, and the second is linked to frm_Link_Waypoints using a filter
in the forms Filter properties. As this little collection of forms stand,
they work just fine. But it is only when I remove them do things work ok
elsewhere. The key form seems to be the 'sub main' form, frm_Links. What I
mean to say is, I tried the process of removing them one-by-one and testing
as I went along, but it is only when I remove the form 'frm_Links ' form do
things work ok elsewhere.
here's is a summary breakdown of the form heirachy:
frm_Runs (overall master form)
frm_Links (linked to frm_Runs) (Main subform and shell for the 2 forms below)
frm_Link_Waypoints (linked to frm_Links)
frm_Road_Restrictions_Links (linked to frm_Link_Waypoints - via filter)
this is the filter for the 'frm_Road_Restrictions_Links'
Run_waypoint_ID_From=Forms!frm_Runs!frm_Links!frm_Link_Waypoints.Form!StreetNameID
Or
Run_waypoint_ID_To=Forms!frm_Runs!frm_Links!frm_Link_Waypoints.Form!StreetNameID
I could try and rebuild it, but I get the feeling that I will simply
replicate the same problem.
well... it's a bit complex, but...
The form is a subform called frm_Links and is on its own tab page and is
linked to the main form (frm_Runs) using master/child [Run_No] for both
settings.
On this form are two other forms. frm_Link_Waypoints and
frm_Road_Restrictions_Links. The first one is linked to frm_Links using
master/child, and the second is linked to frm_Link_Waypoints using a filter
in the forms Filter properties. As this little collection of forms stand,
they work just fine. But it is only when I remove them do things work ok
elsewhere. The key form seems to be the 'sub main' form, frm_Links. What I
mean to say is, I tried the process of removing them one-by-one and testing
as I went along, but it is only when I remove the form 'frm_Links ' form do
things work ok elsewhere.
here's is a summary breakdown of the form heirachy:
frm_Runs (overall master form)
frm_Links (linked to frm_Runs) (Main subform and shell for the 2 forms below)
frm_Link_Waypoints (linked to frm_Links)
frm_Road_Restrictions_Links (linked to frm_Link_Waypoints - via filter)
this is the filter for the 'frm_Road_Restrictions_Links'
Run_waypoint_ID_From=Forms!frm_Runs!frm_Links!frm_Link_Waypoints.Form!StreetNameID
Or
Run_waypoint_ID_To=Forms!frm_Runs!frm_Links!frm_Link_Waypoints.Form!StreetNameID
I could try and rebuild it, but I get the feeling that I will simply
replicate the same problem.
Graham Mandeno said:Hi Eric
OK, so let's focus on this "rogue" form. Is it a linked subform? Is there
anything unusual about it? If it's not too complex, can you recreate it and
see if the problem goes away?
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
efandango said:Graham,
this is a weird one. 2 scenarios:
If I remove the rouge form on the other tab, then the frm_Waypoints and
frm_Road_Junctions work just fine.
I I leave the form on the tab, then the forms in question don't work.
Except
if i move the mouse off the main tab page (which contains a number of
tabbed
pages/forms), and just move it over either one of two text controls, then
the
forms synch together.
I am pretty sure this is not a database corrupt situation, because I have
done this experiment with a new DB, but I do think it is some kind of wird
replicable bug. The problem is consistent and not intemittent. Any
thoughts?
Graham Mandeno said:Hi Eric
Yes, I check my threads regularly, although next week I'm going off for a
couple of weeks' holiday.
Good luck with your detective work!
--
Cheers
Graham Mandeno [Access MVP]
Auckland, New Zealand
Hi Graham,
I think I have found the problem, though not the solution... yet...
I created a new DB and imported the 3 files frm_Runs, frm_Waypoints,
frm_Road_Junctions. and together they worked perfectly. So I began to
import
the other forms, one-by-one... until I think I found the rouge form
causing
the problem, this form is on another tab. I will now investigate that
form
and try to discover what it is that is affecting the other forms. I
will
come
back to you when I have something tangible to tell you. In the
meantime,
do
you check your threads or have them on autonotify? I value your help
and
advice immensely and do not want to lose the connection on this
particualr
problem.
regards
Eric
:
Hi Eric
I have a hunch it may have something to do with the properties of the
'frm_Road_Junctions' form, but I have no idea what properties could be
causing it. Does that form have any filters or any other unusual
settings?
As a test, could you please try creating a new form based on your
Road_Junctions table and insert that into the subform control instead?
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
Hi Graham,
I removed the old subform, and created a new one. I even used the
wizard
(this time) to creat the form. It defaulted to datasheet (which is
fine
for
now), I didn't change any of the forms settings, apart from
master/child
relationship, and this form behaves the exact same way, it only
shows
the
record change when I click on it. I don't think I have a corrupt
database,
everything else works fine, and it's worth pointing out that I have
another
very similar/identical form setup on another tab in the same
database
using
master/child links to another form control and that works just fine.
:
Hi Eric
Are you saying that you see the value in the textbox changing, but
the
record in the subform does not change????
If so, this is most irregular! Can you please try doing a
compact/repair
on
the database, and if it still is not working, try creating a new,
unbound
form and adding the two subforms and the textbox, as I described in
my
NorthWind example.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
Hi Graham,
reading through your northwind example. I checked at this end and
what
I
have reflects what you have at your end.
Yes, I made the linking textbox visible, and yes the record ID's
match
exactly. As I mentioned, it works like clockwork in terms of
linking
the
correct records; they match perfectly, but I have to click into
the
frm_Road_Junctions before it will update.
It's as if the subform only wakes up when I click on it?...
:
Hmmmm... that's a puzzle.
Just to prove it for myself, I set up the following in the
NorthWind
database:
1. Create a continuous form frmOrderList, bound to Orders, with
fields
bound
to OrderID, CustomerID and OrderDate.
2. Create a standard form frmCustomers, bound to Customers
showing
all
fields.
3. Create a new, unbound form in design view. Drag onto it
frmOrderList
and
frmCustomers.
4. Rename the subform controls sbfOrderList and
sbfCurrentCustomer,
respectively.
5. Add a textbox named txtCurrentCustomer, with ControlSource
set
to:
=[sbfOrderList].[Form]![CustomerID]
6. Set the link fields for sbfCurrentCustomer as follows:
LinkMasterFields: txtCurrentCustomer
LinkChildFields: CustomerID
Switch to form view and it all works like clockwork. As I move
through
the
records in the list of orders, the matching CustomerID appears
in
the
textbox, and the matching customer record is displayed in the
subform.
Have you made your linking textbox visible to verify that the
value
in
it
is
changing correctly?
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
Hi Graham,
yes, I did set the master/child setup in the
frm_Road_Junctions,
and
the
ID
numbers to correspond correctly; it's just that the
'frm_Road_Junctions'
doesn't refresh to reflect the new chosen record on the
frm_Waypoints
unless
I click a control on the 'frm_Road_Junctions' form. I even
removed
the
form,
and placed it again using the subform wizard hoping that some
unseen
voodoo
would kick in and resolve it...
to summarise, the link/engine works exactly, just no
refresh?...
:
Hi Eric
Did you set up the master/child link for the subform control
containing
frm_Road_Junctions?
I suggest you make the linking control (txtCurrentWaypoint)
visible
in
the
meantime, for debugging purposes. As you navigate the
records
in
frm_Waypoints, you should see the value in that textbox
changing
to
match
the waypoint ID for the current record. As this value
changes,
the
master/child link should automatically refilter
frm_Road_Junctions.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
Hi Graham,
Yes and No the question relating to the two 'subforms'...
The form: frm_Waypoints is a proper subform, and its
Master/Child
are
linked
to the overall Master form: frm_Runs with [Run_No] on both
settings.
The form: frm_Road_Junctions is not a dependent subform.
It
has
