Results 1 to 12 of 12
  1. #1
    Join Date
    Feb 2009
    Posts
    3

    Question Unanswered: HELP - MS Access 2003 and using 2007

    Hi Guys,

    I am using MS Access 2007 on a few machines that also have MS Access 2003 on (running both because some users are not computer literate so will need training on 2007 when we go fully over to it).
    We run about 5 different databases that were originally built in MS Access 2003.

    1. A database will open in 2007 and work fine. Open it in 2003 and error message 'obect or class does not support the set of events' comes up when trying to access different parts of the database (via a main form)

    2. Another database opens in 2007 and will not open at all in 2003. I had to actually install 2007 to even see the database file.

    Any suggestions on this - in particular point 1?

    Thank you

  2. #2
    Join Date
    Jun 2004
    Location
    Arizona, USA
    Posts
    1,848
    please read item 1 in the Other database server FAQ...

    Access has its own forum, where we'll move this post.
    Lou
    使大吃一惊
    "Lisa, in this house, we obey the laws of thermodynamics!" - Homer Simpson
    "I have my standards. They may be low, but I have them!" - Bette Middler
    "It's a book about a Spanish guy named Manual. You should read it." - Dilbert


  3. #3
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    My first advice is not to go over to 2007 if you can possibly avoid it. It's a mongrel for the developer and users complain a lot about how different it is.

    obect or class does not support the set of events
    Last time I saw that was with a 2007 / 2003 issue that only showed up once moved to 2007. The file was corrupted and I could only fix it by creating a new database and importing all the objects. The corruption never manifested itself until being run in 2007.

    It could also be something to do with Tools - References, but I suspect it might be the same corruption issue that I ran into a short while back.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  4. #4
    Join Date
    Feb 2009
    Posts
    3
    Thanks StarTrekker - I will see what I can do to either get everyone over to 2007 (yep will cause concern as it is different and will require some training!) or get 2007 taken off the computers!

  5. #5
    Join Date
    Apr 2004
    Location
    Sydney Australia
    Posts
    369
    Quote Originally Posted by StarTrekker
    My first advice is not to go over to 2007 if you can possibly avoid it. It's a mongrel for the developer and users complain a lot about how different it is.

    I sometimes wonder whether Microsoft do this deliberately.

  6. #6
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Quote Originally Posted by rdgbge
    Thanks StarTrekker - I will see what I can do to either get everyone over to 2007 (yep will cause concern as it is different and will require some training!) or get 2007 taken off the computers!
    Good There is very rarely any reason to have multiple versions of Access on user's computers. Let us know how you get on!

    Quote Originally Posted by Mike375
    I sometimes wonder whether Microsoft do this deliberately.
    I believe that Microsoft have assumed (incorrectly) that there is no need for Access developers anymore since .NET is around. They have failed to realise that "budget" means something to most businesses.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  7. #7
    Join Date
    Apr 2004
    Location
    Sydney Australia
    Posts
    369
    Quote Originally Posted by StarTrekker
    Good

    I believe that Microsoft have assumed (incorrectly) that there is no need for Access developers anymore since .NET is around. They have failed to realise that "budget" means something to most businesses.
    I have never used A2007 except for the runtime to run what is made in A2003

    What are the basic problem areas when trying to develop using A2007?

  8. #8
    Join Date
    Feb 2009
    Posts
    3
    I havent yet found a lot of problems apart from the ones I have already mentioned.
    But you can't seem to export a report out in excel anymore - well it doesnt highlight and allow you to do so. In A2003 it will export to excel which was always handy when sending the info out to a third party.

  9. #9
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Quote Originally Posted by StarTrekker
    I believe that Microsoft have assumed (incorrectly) that there is no need for Access developers anymore since .NET is around. They have failed to realise that "budget" means something to most businesses.
    I think they've done the opposite - they have put a lot of work into it (XML based file structure, ACE rather than JET, ribbons instead of menus). The problem is that the only immediate and obvious changes suck massively if you've gained any sort of proficiency in earlier versions.

    I hate office 2007. I've stuck with it for months now - I was told that the ribbons are more intuitive than menus after a time, but they aren't. I've lost more time than I care to think about trying to find elemntary functions in these new menus.
    Testimonial:
    pootle flump
    ur codings are working excelent.

  10. #10
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Sounds interesting poots, but with all the work they put into [stuffing] it, where are the benefits??

    XML - big deal. The file bloats more than ever before. A2007 files are just as subject to corruption as previous versions and conversions fail more often than ever. Where is the benefit?

    The ribbon. What a joke. Try customising your ribbon fully and you will find that all of a sudden you in a whole world of pain. Users hate the waste of screen space and are always complaining they don't know where to find stuff. In fact, most users need re-training. Again I have to wonder where the benefit is. Menus and toolbars worked perfectly well.

    ACE vs JET. Not sure on that one. I think there might be some benefits there, but I'm not sure of the real differences yet.

    What are the basic problem areas when trying to develop using A2007?
    Aside from the ones mentioned, I could write a book:

    Just look at rdgbge's post for a start. Incompatibility with Excel in places. What the hell is that?! There indeed are problems with that.

    Inability to easily customise the ribbon.

    Inability to hide the office button.

    Properties on the property sheet are re-organised to make existing users, who knew the property sheet very well, punch screens. Some really stupid stuff there too -- like all the properties for a combo box were in the same area, but now you'll have to scroll the thing just to set up your combo box.

    No user level security.

    Yesterday, I did something I have done for ages: copied some data from Excel and went to Paste Append it in Access. I found that Paste Append is in Home -> Paste (bottom bit of the button) -> Paste Append. What did I get? "The data on the clipboard is damaged and cannot be pasted". Yeah right! Love it ^^
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  11. #11
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Quote Originally Posted by StarTrekker
    I believe that Microsoft have assumed (incorrectly) that there is no need for Access developers anymore since .NET is around. They have failed to realise that "budget" means something to most businesses.
    Quote Originally Posted by StarTrekker
    Sounds interesting poots, but with all the work they put into [stuffing] it, where are the benefits??
    I never said there were any benefits. My point was that they have certainly not neglected Access in lieu of .NET. If anything, I wish they had.
    Testimonial:
    pootle flump
    ur codings are working excelent.

  12. #12
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    No, they haven't neglected Access, just the Access developer! I never suggested they neglected Access!
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

Posting Permissions

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