Access 2007 Runtime problem

Question

I have created a database for a client.  Two machines do NOT have Access installed and one machine has a full version of Access 2007.  I packaged and deployed the database and loaded it onto the client's network.  The packaged solution opens perfectly on the machines that do NOT have Access installed but on the machine that does have Access, I continually get an error message stating: "Microsoft Office Access has encountered a problem and needs to close. We are sorry for the inconvenience".  I have tried putting in the command switch /runtime to open Access in Runtime mode but I get the same message.  I understood that a runtime version would open in full mode on a machine that has the full version installed?......  The path I used for the command switch is:  "C:\Program Files\Microsoft Office\Office12\MSACCESS.EXE" /runtime "W:/path/File_Name".  What am I doing wrong?

Answer 1

Hi Tom - thanks for your reply.  I agree with you that the other computer needs investigating but when I tried to open the runtime (not split) database on MY computer I got the same message.  Mine is in my office and is a stand-alone.  That has stumped me.

Also, I have tried to split the database but have been unable to link the tables to the runtime versions. 

However, today, I split the database and created 3 copies of the front end. Instead of publishing it, I changed the extension (to accdr) on the two front-ends for the machines without Access installed.  I changed the extensions AFTER I linked the tables.  It worked absolutely brilliantly EXCEPT my Customised ribbon does not show on any of the machines.  Now what??  I am so frustrated with this thing.  It is the first time I have ever needed to use runtime and I am finding it very confusing.

I am going to read the article now that you gave the link to in your reply but can you help or can anyone out there in cyber space help???

Thanks so much, ShazzieH

I have looked at the article and it states it relates to Access 2002.  I am using Access 2007, would that make a difference or would it still apply?

Thanks, ShazzieH

Answer 2

You'll have to investigate that computer a bit more. Indeed the same file should be able to run in full version or runtime. Did you set the Trusted Location? Did you run Windows Updates to exhaustion? Did you check with the Microsoft Knowledge Base, including this article http://support.microsoft.com/kb/873266?

One thing that is VERY wrong in your setup is that apparently you have the app installed in a shared W drive. This is likely not the cause of your current problems but you will get other ones soon enough if you don't split the database in front-end and back-end and give every user his own front-end. This is a FAQ so you should not have any problem finding articles about this.

---

-Tom. Microsoft Access MVP