Problem opening Access 2007 on one machine

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • CD Tom
    Contributor
    • Feb 2009
    • 495

    Problem opening Access 2007 on one machine

    I'm not sure where to look for this problem. I have my access 2007 .accdb application. Now when I try start access 2007 on my main computer it will not open. It tries to open with the Microsoft installer, I answer Yes to allow changes, it then starts the office professional 2007 installation, stops in the middle of the processing bar and then goes to the Configuration process for a couple of seconds and then back to the Office professional 2007 installation, starts the processing bar and then get a message "Automatic configuration of the current version of Microsoft Office Access has failed. Your database might not function correctly. This can occur if you don not have the necessary permissions to install Microsoft office access on this computer".
    Not sure what permissions I'm supposed to have. I have a laptop with the same windows 10 and it is works fine on it. I do have office 365 loaded on both machines, so I don't know if there is something with my main computer that is different (there must be) but I don't know what it is.
    I don't know if anyone has run into this problem but it's driving me nuts.
    I make my changes to my application under office 365 but then I have to transfer the program over to my laptop to compile it and create the .accde which I change to .accdr to send out to users.
    I don't like the office 365 Access as it has no packaging part to it. All my users have the Access runtime 2007. I could probably go with the runtime 2016 if there is one and convert my app to this, which I don't want to do if at all possible.

    As always any help is truly appreciated.
  • twinnyfo
    Recognized Expert Moderator Specialist
    • Nov 2011
    • 3664

    #2
    Tom,

    Have you tried using .accde files instead? This requires the full version of Access being available for your users.

    I don't really have a good answer for the heart of your problem, though. just sounds like a software misconfiguratio n, somewhere.

    Or a new Microsoft "feature".

    Comment

    Working...