I finally discovered that there was something else going on after the clock reset. I ended up doing the OIA.XStatus loop and then did a short waithostquiet
It's working, so I'm not going to get too excited.
Has to be good enough, doesn't have to be perfect.
Thanks calculus.
I was using a different approach for the wait routine:
oScreen.OIA.XStatus <> 5
That may have been the issue.
This was mostly being used in conjunction with a problem with errors messing up my macro.
I was using Late binding to activate the Extra objects and everything was working fine. I tried switching over to using early binding and the Attachmate object library and now nothing works as VBA doesn't seem to wait for the screen object to complete tasks before continuing. I'm going back to...
Private Sub Combo16_CmdOk()
Dim rst as recordset
If Me.Combo16 = "Delete"
set rst=me.recordsetClone
rst.Delete
me.Requery
End If
ExitHandler:
If not rst is nothing then
rst.close
set rst=nothing
ENd if
End Sub
1) Make sure you name your controls something useful rather than the generic names generated by Access. You'll thank yourself later when you have to go back and fix something.
Dim rst as recordset
set rst = Me.RecordsetClone
rst.Delete
Me.Requery
Make sure to destroy the rst object before...
You will probably need to use a grid, rather than a datasheet. This will require having a copy of VB6 or VB.Net and creating a custom control.
Beyond that, I'm not able to be much help.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.