The form is normally opened by the statement
DoCmd.OpenForm strArgument, acNormal, , , acFormAdd
in a switchboard event procedure. In the form's property sheet the default view on opening is Single Form, and Allow Form View is set. Debug.Print statements in the various event procedures of the form opening sequence (Open - Load - Resize - Activate - Current) (which contain no other code than the debug.print statements) show that when the form opens incompletely the Open, Load, Resize and Activate events occur, but not the Current event. After the Activate event the form is displayed with a blank Detail section.
Compact and Repair, Decompile and recompile don't help. It's doesn't appear to be data-related because I have had it occur with three different users' back end data files.
Sounds like either a tricky hardware problem or a timing issue, right? But it's not hardware, because it has occurred repeatedly on two different computers (mine and the user's) in different locations running different compiled and uncompiled versions of the DBMS. I have also caused long pauses in each of the above-mentioned event procedures (by inserting MsgBox statements there), and it didn't make any difference. Neither did Google turn up anything helpful.
I don't expect anybody to be able to solve this with such scanty information, but can anyone suggest any further way I might be able to tackle the problem or get further information? Or has anyone seen any similar behaviour?