A
Adam
This is a continuation of post I started here on 12 July, with some more
information.
My problem was that Access 2000 had stopped giving error messages: when it
came to a bug in my code, it just silently stopped executing. You can
imagine how hard that made it to debug anything.
I think I have now found out what is causing the problem. It seems to be to
do with the AllowSpecialKeys property in the startup options. I had disabled
this option, and that was when the error messages stopped. If I switch it
back on, the error messages start again. If I switch it off again, they stop
again. It seems pretty reproducible.
Has anyone come across this behaviour before? Is there anything that can be
done about it, other than keeping the AllowSpecialKeys property enabled
until right at the last minute once I am sure (well, OK, mostly sure) that
there are no bugs left in the code?
Many thanks
information.
My problem was that Access 2000 had stopped giving error messages: when it
came to a bug in my code, it just silently stopped executing. You can
imagine how hard that made it to debug anything.
I think I have now found out what is causing the problem. It seems to be to
do with the AllowSpecialKeys property in the startup options. I had disabled
this option, and that was when the error messages stopped. If I switch it
back on, the error messages start again. If I switch it off again, they stop
again. It seems pretty reproducible.
Has anyone come across this behaviour before? Is there anything that can be
done about it, other than keeping the AllowSpecialKeys property enabled
until right at the last minute once I am sure (well, OK, mostly sure) that
there are no bugs left in the code?
Many thanks