The "disappearing" subform

[BRMorgan]

Anyone have an idea on this one? I created an Access 2003 (SP3 + hotfixes) form with a subform. On my machine it works fine. Both load initially and all is right with the world. BTW, I'm running XP SP2. When I run it on an identical machine (same model, same os, Access 2003 - same SPs & hotfixes on both) the subform does NOT load initially. This causes as AfterUpdate event error because I reference the subform in the AfterUpdate of a combo box on the Parent form. Here's what I've tried: - I did have 2003 & 2007 installed on mine. Removed both, including all Registry references & did a clean install of 2003. Even without the SP & hotfixes it would NOT error on mine.- Recreated both the form & the subform from scratch - took a long time, but I did not even cut & paste code just to be sure. No dice.- Created a new blank project with only the data, form & subform. Nada.- Reinstalled 2003, SPs & Hotfixes on the other machine - ARGH!!No mater what I do I cannot make it fail on mine & cannot make it work on the other machine (actually its 10 other user machines it won't work on). Oh - if I open the form in design mode on one of the failing machines THEN run it - voila - success. Happens with both the mde & mdb versions.I'd apreciate any insight or suggestions - at the end of my rope - and that NO April Fools! :-)

[RuralGuy]

Put a diagnostic MsgBox in the SubForm OnLoad event and report the RecordCount of the Recordset.

[BRMorgan]

RuralGuy,
Thanks for your suggestion. I did & on the "good" machines I had a recordcount. On the "bad" machines I got the error that the field was unknown (back to not seeing the subform). trying your suggestions & some from another forum, I got a light bulb! I removed the linking between Parent & Child and made the child invisible. In the load event of the parent, I coded the desired filter, requeried the subform, and made the subform visible. This actually worked better, b/c the client added another criteriea (the ability to filter the subform by a group of expired dates - ex. 30 days out, 90 days out, etc).

Who knows why the original way worked on some machines and not others, but at least I can roll this out. Then I'll have time to ponder it more.

Thanks to you for offering suggestions. I'm alone here & sometimes it just takes "talking" it out & getting ideas from others to find that "Ah-Ha" moment.

[RuralGuy]

Outstanding! You always learn more when you work it out for yourself anyway. Glad I could be a catalyst here.