M
Michael_Brooks
I am experiencing an intermittent problem that is causing me to pull my hair
out.
It seems to centre around a forms own code, say on a button, when it makes
an external call to a module function within the same db or library function,
then all vb code just stops executing!!!. It really does just stop executing.
Once this cycle starts even the STOP instruction fails and I can not go into
debug to single step through the code to see where the problem is. The left
mouse click against the programme line to halt execution does not function
once this cycle has started.
I can’t get into debug mode to single step through the code to find the
problem.
My code look OK but there must be something that it does not like.
Code runs up to the point of the external call (external to the form object)
but then TOTALLY stops
The db code compiles OK.
It is an intermittent problem but has always been lurking in the background.
I have never had this on earlier versions of Access.
Could anyone please help before I am totally bald?
Michael Brooks
out.
It seems to centre around a forms own code, say on a button, when it makes
an external call to a module function within the same db or library function,
then all vb code just stops executing!!!. It really does just stop executing.
Once this cycle starts even the STOP instruction fails and I can not go into
debug to single step through the code to see where the problem is. The left
mouse click against the programme line to halt execution does not function
once this cycle has started.
I can’t get into debug mode to single step through the code to find the
problem.
My code look OK but there must be something that it does not like.
Code runs up to the point of the external call (external to the form object)
but then TOTALLY stops
The db code compiles OK.
It is an intermittent problem but has always been lurking in the background.
I have never had this on earlier versions of Access.
Could anyone please help before I am totally bald?
Michael Brooks