Use of Access Runtime to open a database on another computer on a network

[Joe Wharton]

Is it possible to use Access Runtime to open and write to an Access 2010 database file existing on another computer in the same Homegroup? If so, is any programming necessary on either computer for the Runtime computer to see the database file on the host computer?

[CJ_London]

If so, is any programming necessary on either computer for the Runtime computer to see the database file on the host computer?

yes - you would need to create the equivalent of the external data, link to file facility on the ribbon

see this thread

https://www.accessforums.net/showthr...633#post340633

it's linking to excel using transferspreadsheet, to link another db you would use transferdatabase instead

[Joe Wharton]

yes - you would need to create the equivalent of the external data, link to file facility on the ribbon

see this thread

https://www.accessforums.net/showthr...633#post340633

it's linking to excel using transferspreadsheet, to link another db you would use transferdatabase instead

Thanks for the reply. I'm afraid I don't have the expertise to do, or even understand what you are suggesting. I can't code in Access, so everything I've done was by using the onscreen menus and tools. Would the need to do what you suggest be eliminated if I bought another copy of the full version of Access and installed it on the second PC?

[CJ_London]

it may be possible in runtime using a macro, but I don't use them so can't help in that respect.

If you bought another full copy of Access, the user would still need to know how to use the ribbon.

However I took from your post this was an occasional requirement to open and update. If you are talking about a multi user situation where two users are using the same data all the time. You would need to split your database into front and back end (basically tables only in the back end, everything else - forms/reports etc - in the front end. Then in your copy, link the front end to the back end (see external data tab on the ribbon). Providing you are using a common path, you can then just give a copy of the front end to the other user.

So providing your user interface is designed purely to work through forms and reports and you have set an initial form to open automatically when the db is opened, your user can work using runtime.

Be aware that a user with runtime does not have access to the ribbon, navigation window or shortcut menus (the dropdowns when you right click), but like my suggestion in my first response, the equivalent can be created in code.

[CJ_London]

One other suggestion, if you want to see what it is like to use runtime, change the file extension of your app from .accdb to .accdr. Then open the file - however it works is how it will work in runtime 'proper'. When done, exit the app and change the file extension back to .accdb

[Joe Wharton]

yes - you would need to create the equivalent of the external data, link to file facility on the ribbon

see this thread

https://www.accessforums.net/showthr...633#post340633

it's linking to excel using transferspreadsheet, to link another db you would use transferdatabase instead

It sounds like my easiest solution is to buy a full copy of Access 2016 for the second PC, which is running Windows 2010. However, the copy where the database resides is on a PC running Access 2010 under Windows 7 Professional 64 bit. Access 2010's file extension is .mdb, and it appears that Access 2016 has a file extension of .accdb. Would Access 2016 be able to access the .mdb file on the main computer or are they incompatible? Also, what is it that I need to know how to do with the ribbon?

[CJ_London]

The windows bit is irrelevant, what matters is both versions of office/access need to be the same (32 bit preferred/recommended). Your comment about 2010 being mdb rings alarm bells - it should be .accdb so perhaps this has been developed in a much earlier version of Access, in which case 2016 may not be able to open the file - it depends on what version of mdb. I think 2016 will read a 2003 mdb but not 97 or 2000 which is now pretty much fully deprecated.

what is it that I need to know how to do with the ribbon?

how to link to another database - see External Data>Access Databases.

Note also that any development done in 2016 may not be readable in 2010. And if you have not split your db, and the 2016 user opens the file, it will automatically update it to 2016, so the 2010 user is 'locked out'. If the db is split, and each user has their own copy front end linked to the back end, this will not be a problem since the table element of access is the same.