Access 2010 Runtime - Link to backend database

and having trouble sourcing information that makes sense.

I have a database that is split into a front and back end.

The back end is to reside on a shared network location (yet to be determined but we'll call it \\SERVER\DBSHARE for now).

The front end will be installed on the client workstations.

The Client workstations have mixed versions of Access 03 and Access 07 but all have the Access Runtime 2010 installed.

The problem is when you open the front end it spits an error out saying it can't locate the backend. As this is the Runtime version there is no Link manager to set the path.

I'm assuming (and this may be wrong) that there is a way, somewhere be it the package manager, code, pathfile to be able to say something like "Path to Backend is \\SERVER\DBSHARE\be.accdb"

Does anyone know if there is some way to set the path so that the backend can be linked when using Access Runtime

Sponsored Links:

Related Topics

How to re-link tables
I have a database with the frontend and backend on same network. Now when I have to do changes to it I take a copy of the frontend or backend home and re-link the table on my computer.

Now when I finish it all I want to be able to do is email the frontend or backend to someone without having to drive out there and this computer only has access runtime installed. So I have to go up there, bring my laptop, access their server, and link the database on my laptop, then take the files and drop it on their computer

I would like it when I email them the files an option could pop up to re-link the files since they are just using access runtime


Frontend/backend: Writing data not working on some computers
SERVER1 - Holds the database back end. Permissions on the database file (And folders it's in) are full access for everyone.

COMPUTER1 - Windows 7, this computer originally created the database using Access 2010 Professional. This computer runs the front end of the database successfully, no problems.

COMPUTER2 / COMPUTER 3 - Windows XP running Access 2010 Runtime / Windows 7 running Access 2010 Runtime. These computers both get a security warning when opening the database. They read data fine, but do not write any data.

No error message is displayed / nothing to indicate that there is a problem.


Access 2010 Ribbon - Runtime
We are in the process of upgrading from Access 97 to Access 2010

The database admins have a full copy of 2010 and the general users will have a copy of the Access 2010 runtime installed.

The issue is that when a database is opened in the runtime, the ribbon disappears, this is preventing people from exporting datasheet views to excel etc.


Linking frontend access into SQL database
I have a access 2010. Database which I split into frontend and backend which works well.

I have decided to move the database into SQL, I used the export wizard and moved the database into SQL which seemed to work, and it I look at the backend which SQL made I seem to see mydata, and if I open SQL it seems to be in that to.

But my problem is, how do I link the access frontend to the SQL backend.


2010 Runtime ADODB Connection Failure
I have a routine which connects to MySQL database with ADODB connection. This worked in 2003 and 2007 runtime but throws a 430 error on 2010 runtime. It works in full access 2010. Has there been a change of policy to restrict this type of connection in the 2010 runtime?

If I use a linked ODBC table instead of ADODB the runtime fails with "Runtime Error". It still works in full access


access 2010 windows7 nas linked tables
Have had 4 new pc.s(windows7 office 2010) connected to a network attached storage device.
Database has a front and backend, with backend, on the nas, tables linked.
All pc's link with no problem.
Three of the pc.s if you turn them off, the frontend loses its connection to the backend linked tables.
If I go into external data and look at the mapped conection, it has a red cross, although I can see the network drive and the backend tables from my computer. If I click on mapped conection, the red cross disappears and the link works.
This happens on three of thefour pc's.
Any one have a clue whether this in an access/windows or network problem


Runtime access 2010
I need a beginners tutorial on the use of Runtime - I have access 2010 installed - I think I downloaded and installed access runtime for 2010 - for the life of me I cannot find any references to runtime in access or in windows list of programs.

I tried to publish the DB but all I got was a accde extension not the accdr.


Access 2010 Runtime Database
I want to deploy a single user database to one laptop which has a fullly blown version of Office 2010 on it.

Can I still install runtime on this machine and produce a runtime version of the database


Depolying ACCESS 2010 runtime
The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes code from modules, forms and reports.

You should back up your database before attempting to open the database and delete the VBA project.

My developing environment is Office 2007 ACCESS 2010. My runtime environment is Office 2007 RUNTIME ACCESS 2010.

Both ACCESS Development and Runtime are under SP1 32 bit


Runtime 2010 ADODB Connection failure
I have a routine which connects to MySQL database with ADODB connection. This worked in 2003 and 2007 runtime but throws a 430 error on 2010 runtime.

Error 430: Class does not support Automation or does not support expected interface

It works in full access 2010. Has there been a change of policy to restrict this type of connection in the 2010 runtime? If I use a linked ODBC table instead of ADODB the runtime fails with "Runtime Error". It still works in full access.


Runtime 2010 ADODB Connection failure
I have a routine which connects to MySQL database with ADODB connection. This worked in 2003 and 2007 runtime but throws a 430 error on 2010 runtime.

Error 430: Class does not support Automation or does not support expected interface
It works in full access 2010. Has there been a change of policy to restrict this type of connection in the 2010 runtime?

If I use a linked ODBC table instead of ADODB the runtime fails with "Runtime Error". It still works in full access.


Access RunTime 2010 security settings - "The RunCommand action was canceled"
How can I change the security settings of Access RunTime 2010? We have an access database that users had successfully used when they had the full version of the Access program. They arenow using Access 2010 RunTime, and when they click on a specific button (which runs a few different macros) in the database, they receive a message that says "The RunCommand action wascanceled." Are there any settings in Access 2010 RunTime that I can change (possibly in the registry) that will allow the RunCommand action to work and not be canceled?


Access Runtime 2010
What am I missing with Access 2010 Runtime?

I have a small database I would like to distribute to a few people who don't have Access. I published that database as an ACCDE.

I installed Access 2010 Runtime on a co-worker's machine as my test case. I copied the new ACCDE also on that co-worker's computer. When I tried to open the ACCDE, it opened but none of the tables/forms/reports were visible.

What am I missing? How do I easily distribute databases to those without Access? Is there something special I need to do


Access 2010 Runtime crashing database
I have a different thread up regarding problems installing the Access 2010 app (hope that get's solved), but I actually found a user whose workstation has it successfully installed (unfortunately, he doesn't know how)?!

Now when we try to run my db on it, whenever a combobox or command button on a form is clicked, the app crashes. I checked and he's running Office 2010 v14.0 32-bit (the Access 2010 Runtime is the latest one from MS, published 5/10/2010).


Linking tables from password protected Backend db
In my Frontend db, I use 'J Street Access Relinker' (link), as suggested in another post, to link to my Backend db.

If I protect my Backend db with a password, from the Security menu in Access, it is no longer possible to link to the Backend db, or at least the Frontend can't open the links.

It there a way for me to set the password via code in my frontend db, so the linking can be done


How do I open access in runtime without security warnings?
I am in the process of upgrading from Access 2003 to 2010 the current databases are split and users run the application in runtime.
I have been able to upgrade successfully except for the Security Warning I get when opening the database in runtime.
Have tried changing settings in the Trust Centre, this has fixed the Full Access security but seems to have no effect on Runtime.


Access Runtime
Access 2007 & 2010 runtime. Has anyone used the runtime versions? I have an access report that uses a csv file for data. It works fine under the full version but the runtime does not open it


Questions about splitting a 2010 Access database
I have read through some of the other threads on this subject and I am more confused than ever.

I have split an Access 2010 database with the tables being in the backend. Some of these tables were originally imported from an Accounting database. Before I split the database, I had aseries of macros that would delete these "Accounting tables" and then import the latest version of these tables from the accounting database.

I need to continue to update those tables on an on-going basis. As a result, I created a startup form that had a control to backup the database and another control to run the macros to update the accounting tables.

I then opened the front end and relinked all of the tables in the back end to the front end.

From what I have read, I believe that I should not have done that (I.e. the backend should contain tables only- no macros, forms, etc.). If that is correct, what is the proper way to deal with these tables that need to be replaced on an ongoing basis? I know I can link the accounting tables from the accounting database to tables in the backend (rather than import them) but Iwould rather not do that for a variety of reasons.

can I use VBA or macros or something in the front end to do these updates at a click of a button?


Access 2010: Frontend with VBA and backend change breaks VBA form calls (onLoad etc)?
When I have a frontend with VBA (for table additions etc) and a backend (all tables except Switchboard Items), when I change from my test-backend (USB) to the realtime-backend (Network drive/directory) the tables work, but all VBA calls (events like onLoad etc.) break (i get an error message). The only way I can fix it atm is by using the Compress and repair database, which restores the links between VBA and the forms etc.

What causes this to happen? Is it a known bug in Access 2010?


Backend folder vs. frontend database
If I have an MS Access frontend that connects to an MS Access backend, is there a way to hide/permission block the pathway to the backend's folder but still allow access via the frontend db?

Right now I can't dedicate a server to a more "secure" form of DB or anything like that so I'm stuck with MS Access for now. say, a link table path and then navigating to that folder and getting access to backend information. What might be some solutions to this?