There is a bug in both 97 and 2k versions. In order to be sure that what Access understands is what you really mean the surest thing to do is passing it the date like "#27/mar/2003#". As I looked around this is the only way you don't risk to mess it up.
sometimes access forms need refresh. try to insert in the code for afterupdate of the control you work with something like
"....
me.refresh
..."
Also be sure you haven't another instance of the form running as a subform or so.
I tried all solutions I found for 2486 and none of them worked.
It's something about the way that Access initializes the form classes. If you try to docmd.openform or docmd.close on a higher irq object (such as a query) you will get the darn 2486.
The only way you can avoid this is to...
Don't think problems. Think solutions.
Why should your web app insert the data into some forms when you can easily put the data directly into tables and web-server variables.
Try using ADO connections. It is not very GUI but it is simple to do and also works OK.
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.