DoCmd.Openform Fails on dual Proc Machine

[erict]

Access 2002-2003 runtime

App works fine on single proc machines but we are rolling out a tech refresh and we found this case where the code appears to simply slip through the open form command and the form never opens.

If Not IsNull(frmPODet ails.Form!txtPO Number) Then
MsgBox "frmPurchaseOrd ers Open Form"
DoCmd.OpenForm "frmPODetailsUn bound"
End If

Note since this is a production issue Ihad to uses message boxes to see where we get. I also included message boxes in the frmPODetailsUnb ound load event. these were never fired off.
I hae been able to recreate on a few dual core machines but not all.

Example Fail Spec
MS Windows XP Pro Version 2002 SP 2

Intel Core 2 Duo CPU E4600 A 2.40GHz 2.39 Ghz. 1.98 GB ram

But works on this spec
XP Pro Ver 2002 SP 2
Intel core 2 Duo E4400 2.0 GHz 2.0 Ghz 1.98 RAM

I suspect a race condition but there are no do events calls in any of the code that I can see.

Any thoughts would be appreciated

[missinglinq]

When apps run fine on one machine and not on another, such as a new machine with a new copy of Access, the first thing you have to think about are missing references.

Here are Doug Steele's detailed instructions on how to troubleshoot the problem:

*** Quote ***

Any time functions that previously worked suddenly don't, the first thing to suspect is a references problem.

This can be caused by differences in either the location or file version of certain files between the machine where the application was developed, and where it's being run (or the file missing completely from the target machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the Debug Window, using Ctrl-G, provided you haven't selected the "keep debug window on top" option). Select Tools | References from the menu bar. Examine all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect them, and back out of the dialog. If you really need the reference(s) you just unselected (you can tell by doing a Compile All Modules), go back in and reselect them.

If none have "MISSING:", select an additional reference at random, back out of the dialog, then go back in and unselect the reference you just added. If that doesn't solve the problem, try to unselect as many of the selected references as you can (Access may not let you unselect them all), back out of the dialog, then go back in and reselect the references you just unselected. (NOTE: write down what the references are before you delete them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out

http://www.accessmvp.c om/djsteele/AccessReference Errors.html

Just so you know: the problem will occur even if the library that contains the specific function that's failing doesn't have a problem.

**** End Quote ****

Welcome to Bytes!

Linq ;0)>

[erict]

Actually This is the only place in the app where the OpenForm command fails. But I will try what you stated and see what happens

[erict]

I resolved the Issue but I am not sure how. All I did was stare at the single line of code cursing access.

Oh yeah I recompiled it and it ran.

Thanks