Re: Object or class does not support the set of events?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

After searching for clues and trying everything I could, I think I managed to
stop the errors from occuring. The decompile tip was very beneficial--big
thanks to Larry Linson on that one. Unfortunately, my problem was more
involved but while finding the syntax for the decompile, I came across some
tips on finding corruption. Recreating the database and importing didn't
solve the problem, but what did was the SaveAsText option. Here is an
excerpt from a post by Allen Browne regarding this:
----
"Something else you could try with the suspect objects is to save them as
text, and then import them from the text file. For example, to save Form1
from the corrupted database:
SaveAsText acForm, "Form1", "C:\form1.txt"
Then in the new database:
LoadFromText acForm, "Form1", "C:\form1.txt"
----

That process should give you a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, the reference ambiguities are
resolved, and know each step is okay before moving on to the next one."

Also, searching the newsgroups for "corrupt" or "corruption" will give you
more information on these issues. Someone correct me if I'm wrong, but it
appears that the tables and forms in Access somehow lose their "link" with
the underlying VB code and try to refer to event procedures you may have
removed in the past (or not have implemented at all.)

SaveAsText/LoadFromText looks like a last-resort solution but it may be the
one thing that fixes your database after trying everything else. Good luck!

Bill K

"bhwithun" wrote:

>
> I am also working on a Microsoft Access database and receiving this same
> odd error. Not too much out here for clues as to what's wrong. I am
> using Windows XP, Access 2000. In my case it's rather simple. I have
> a table that I can interact with manually and with forms, but when I
> try to place an event procedure on a form field, I get the error you
> mention at runtime.
>
> The event procedure can even be EMPTY, with no instructions. I don't
> see how database corruption can account for this, but then who knows.
> The application works perfectly, but if I try to put any kind of event
> procedure on any kind of keyboard event, bam!
>
> I have not gone through to figure out if ANY event will cause this
> error, or if this particular event will crash on ANY form field, but I
> am running out of other creative debugging ideas and will soon get
> around to trying that. If I make any progress I will be quick to post
> the solution. Short of that I will post any ideas or tips I may run
> across.
>
> Good luck with your debugging.
>
> Brian Herbert Withun
> Carleton, MI
>
>
> --
> bhwithunPosted from http://www.pcreview.co.uk/ newsgroup access
>
>
.

Relevant Pages

  • Re: [Event Procedure] Code Behind Form
    ... For suggestions on avoiding this kind of corruption, ... From time to time a form's [Event Procedure] property text in the ... And, in a particular Access database, the entire code behind the form ... Database developed on a Windows XP and then moved to Windows Vista ...
    (microsoft.public.access.formscoding)
  • Re: [Event Procedure] Code Behind Form
    ... Sometimes you cut a control from a form, and then paste it back in When you do that, the code becomes disconnected, and you have to set its event properties again to connect the code to the control. ... I then modify that codes as needed and then compile the code which I believe creates the [Event Procedure] text for each event that may be called from the event procedures found in the pasted code. ... And, in a particular Access database, the entire code behind the form sometimes comes up missing. ... Database developed on a Windows XP and then moved to Windows Vista Ultimate which now with SP1 ...
    (microsoft.public.access.formscoding)
  • Re: How to delete procedure
    ... If you have a database where you deleted the form, ... Still in the code window, choose Compile from the Debug menu. ... I create an event procedure, ...
    (microsoft.public.access.formscoding)
  • Re: Event Procedures Stopped Working
    ... Open a code window, ... If that still does not solve the problem, the database is partially corrupt. ... Compile the application. ... Now every>> time I do something which will start an event procedure I get this message:>> "Procedure declaration does not match description of event or procedure ...
    (microsoft.public.access.formscoding)
  • Re: Too easy to change data
    ... this subjuect - I would like to be able to make mass chages in the database ... event procedure in its' OnClick event, and add the following code to the ... editing, click the button to "allow edits", make the change, then click ... That would allow filtering, but not editing. ...
    (microsoft.public.access.security)