2010 Runtime app freezes on form load

[DaveMarvin]

Hi all:

I'm developing a split Access/SQLite FE/BE app. I'm developing in (32-bit) Access 2010 on Windows 7. Multiple clients will use the Runtime engine on their WinXP machines running Office 2003/2007/2010.

Following the latest round of development, some previously-tested functions "suddenly" do not work in the Runtime environment. The most obvious is a link from one form to another pop-up (modal) form window. The link works fine in the development environment, but when I attempt to link to the modal form from the Runtime environment 1) the main screen refreshes, 2) the modal form does NOT pop up, and 3) the Runtime application locks up, requiring a three-finger salute to kill the application. These links worked swell last week; following the changes (to other code) in the latest build, I can't figure out what's going on with the links this week. There's been no change to the calling sub in the parent form (although I DID create a new On_Current event); there's no code present in the child form to change.

I've attached three images. Main_Form.jpg shows the calling form. Notice that there are two columns formatted as hyper-links (the links are actually activated by On_Click events). Clicking on a linked transmitter value in the left column pops up a transmitter detail form (shown in Main form - Transmitter detail.jpg). These links work as usual in both the development and Runtime environments. Clicking on a linked Release Group ID in the right column is supposed to pop up a Release detail form (as shown in Main form - Release detail.jpg). This is the form that fails to render and then locks up the Runtime application.

Before we get in a discussion of whether or not I'm correctly calling the pop-up forms, please note that they have worked,just fine in both the development and Runtime environment for the last two months, until the latest round of code revisions. That said, here's the code that calls the two pop-up forms.

Private Sub Release_Group_ID_Click()
   '// This is the form that doesn't render in Runtime
   DoCmd.OpenForm "f_Release_Group_Detail", acNormal, ,
      "Release_Group_ID=" & Release_Group_ID.Value
End Sub

Private Sub Transmitter_ID_Click()
   DoCmd.OpenForm "f_Tagged_Fish_Detail", acNormal, ,
      "Transmitter_ID='" & Transmitter_ID.Value & "'"
End Sub

I tried replacing the calling filter clause with an OpenArgs parameter in the calling form, and then setting Me.Filter=OpenArgs in the destination form. No go.

I created On_Open, On_Load, and On_Current subs in the "f_Release_Group_Detail" form, just so I could add MsgBox calls. I get messages from all three events (twice from On_Current) before the application locks up under Runtime. This suggests to me that the call from the pop-up is loading, but "hidden", and since it's modal I can't do anything else within the application. Again, this ONLY occurs in the Runtime environment.

I triple- and then quadruple-checked that I was retrieving valid data from the underlying query, and then created a new form that contained just the Release_Group_ID control. Still No Go.

I decompiled and compacted/repaired the application (thrice). Still No Go.

I have focused on the malfunction of this one form, because I have a link to this same form another parent form that exhibits the same behaviour (failure to launch and then lock-up of the Runtime environment). I have also discovered similar behaviour in a report, where a linked detail form fails to launch. In this second case, the application does not lock up. So far, all other functionality appears to be normal. I can't wait to see what next week's revisions trigger!

I of course have an archived version of the application prior to the latest revisions, when everything still functioned properly in the Runtime environment. Can anyone suggest how I can incorporate my latest (and future) revisions without jeopardizing the existing functionality?

 

[thechazm]

The fact that your application in the run time environment flashes leads me to believe the that form that your calling opens but "and this may be a far shot" have seen in the past that depending on the way the code is executed in the runtime environment it can cause the popup windows to be pushed behind the main form and make you believe its locked up because its waiting for the input or the closing of the form before you can do anything else.

I would suggest to make sure that once your form in open that all your other code stops from running or have nothing running outside of that window that will shift the focus away from the popup window.

Again this is a far shot but it sounds very simalier issue I faced in the past.

Almost forgot as well when the window opens force the focus to the form that you want displayed after its open to make sure even if it gets pushed behind it will get put back on top.

 

[DaveMarvin]

Thanx. It does sound like a ling shot, but I'll try damn near anything at this point.What's the sure-fire way to ensure that a control in my modal form receives focus when the form is launched?