Results 1 to 11 of 11
  1. #1
    Lounger
    Join Date
    Mar 2010
    Location
    UK
    Posts
    47
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Morning Loungers!

    Sorry i cant elaborate more, but i dont even know the cause of the problem, all i knwo is my database worked fine this morning, i exported a couple of queries. and then all of a sudden i got this error:

    "The expression On Click you entered as the event property setting produced the following error: Object of class does not support the set of events."

    this is funny that it says on click isnt supported by a button (i clicked a button to get this particular error message)

    This happens for everything i use, weather it is an on open event, an on click event or an after update event.

    Does anyone know a potential cause!? and maybe a solution, as i am really confused!

    Thank you.

  2. #2
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts
    Have you tried Compact and Repair?
    Regards
    John



  3. #3
    Lounger
    Join Date
    Mar 2010
    Location
    UK
    Posts
    47
    Thanks
    0
    Thanked 0 Times in 0 Posts
    just did, no joy

    the problem has started spreading to other databases, so i think it might be something with my actual machine.

    some genius actually started using office 2007 on my machine (which i dont do as that may screw things up), would that have something to do with this? would it have edited the code to meet 2007 standards, thuisly making it unreadable for 2003?

  4. #4
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts
    Could be..

    Check the References.

    Go to the Visual Basic Editor (Alt + F11), then Tools...References.

    Do any of them say Missing?

    Try a Decompile, then Compile again.
    Regards
    John



  5. #5
    Lounger
    Join Date
    Mar 2010
    Location
    UK
    Posts
    47
    Thanks
    0
    Thanked 0 Times in 0 Posts
    all the refferences are there, none say missing, and from what i can rememebr they are the same names aswell.

    As for decompiling, after a quick look at the link, i dont think i will be able to do that due to over zealous IT restrictions. But i will be having a chat with them.

  6. #6
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts
    Is it possible that your reference for Access is set to the 2007 version, but you are trying to use 2003? 2003 isn't smart enough to change that if it has been set - look for version 12 - if you find it change it it version 11.
    Wendell

  7. #7
    Lounger
    Join Date
    Mar 2010
    Location
    UK
    Posts
    47
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I can't find version 11.

    but i have previously been using 12 with no problems, that was/is the source of my problems with regards to the emailing code in another thread.

    I think a possible uninstallation of 2007 is required, it seems to be causing more problems than solutions.

  8. #8
    Lounger
    Join Date
    Mar 2010
    Location
    UK
    Posts
    47
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Sorry for double posting,

    the databases work in 2007, i feel a bti stupid for not trying that first.

    That implies that it is indeed a problem with the dual suites we have installed on this machine. I woul get them removed, and just hope that fixes the problems.

    however, as others are having problems with databases i have opened (not even saved! just opened!) i doubt that will actually do a darn thing!

  9. #9
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts
    I have both 2003 and 2007 on the same machine, but mostly use 2007. But to open dbs in 2003 I often need to decompile.
    So just removing 2007 will not fix the problem by itself...but it will stop it coming back after you fix it.
    Regards
    John



  10. #10
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts
    Just another take on this.
    I run a machine with Access 2003 and 2007 installed.
    If I use 2007 then I have to do a repair on 2003 before I use it,
    or all manner of weird VBA Errors start to happen.
    Then everything is ok until I need to use 2007 again.

    Recently I installed Access 2010 on same machine.
    All are usable, but 2003 issue still appears to exist
    if I use 2007 or 2010.
    Andrew

  11. #11
    Lounger
    Join Date
    Mar 2010
    Location
    UK
    Posts
    47
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I have had access 2003 reinstalled and 2007 uninstalled, that may seem like a typical "Bah i dont know whats happening" kind of reaction. But it has fixed my problems.

    When 2003 qand 2007 were installed there was a registery key hack put in place to stop this happening, turns out, the person who installed poffice on my machine forgot to do that! hense all these problems!

    Thank you for your help guys!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •