Null error is gone but I'm getting something else now. I will work through the latest and see what I can conclude...might be back! Thanks for your assistance!
After the combo box which gives the error the next tab stop is for WorkLoadUnits. This just started after upgrading to 2010. So there may be other code that is calling this sub too soon?
The reason I ask is that after entering the suggested code, the offensive line became the very next line...
Apologies! New to VBA and coding forums. See red text.
Private Sub fsubProductivityInput_Calculations()
On Error GoTo err
'Calculate Breaks and Net Hours
Dim frmLines As Double
Dim frmHours As Double
Dim frmLPH As Double
frmLines = Me.WorkLoadUnit
frmHours = Me.Hours...
We just upgraded to Office 2010 from 2003 and I am now getting 'invalid use of null' after choosing a valid combo box option. When I debug, the line that highlights has to do with a text box on the form rather than the combo box. Here's the code highlighting:
frmLines = Me.WorkLoadUnit...
I've been trying to hold 8 Access dbs together for about 2 years. They were built in 2000 then upgraded to 2003 with no issues. We just upgraded to Office 2010 - exciting right? Well, not so much... ;)