Setting up Database with Access Runtime

Question

Can anyone help? I'm trying to set up a database using Access Runtime at my place of work, at home and for friends, I've been able to set things up no problem. We have 2 separate systems at work, one with Access 2010 [Pc1} (soon to be upgraded to 365) the other[Pc2] without, so is running Access runtime, my database does run on Pc2, but only one person at a time can use it. So here is where the problems start, Yes needs to be split, done all ok tested on Pc1. Getting backend and front end on to Pc2 mmm!, So using Pc1 running Access 2010, using Visual Basic would write some code and at some go to, Tools tab, References and choose from the list get the relevant reference and all sorted, well our 'IT' have chosen, not to give us the ability to use these references at all, so when I click on Tools drop-down menu, then click on References no drop-down menu at all to select from. Is there another way of setting my split Db on Pc2

Answer 1

The issue isn't your IT, it's runtime.  Runtime is a striped down version of access made to run an existing database, but not to do development work.  For all development you need the full version of access.

In your scenario, you mention 2010 and 365.  This you must do all your development in the oldest version, so 2010, to ensure it runs for all your users.  So you need to do all your work on PC1

In such a scenario, you want to place the back end in a shared folder, accessible by all your users/PCs, and then distribute a personal copy of the front end to each user (never share a copy of the front end otherwise you'll be in front problems).

As a side note, office 365 had been horribly unstable do to bugs in almost every single update.  If highly recommend you disable updates and manually update things in a knowledgeable and controlled manner.

Answer 2

Late Binding Of course thanks guys for your patience with this 60 Year old just learning Access, Late Binding Doh!

Answer 3

The Access Runtime would not allow you to manage reference issues. The Runtime is, essentially, Access without the design time elements. In order to properly deploy your database to the Runtime machine, you'd have to ensure those references exist on that machine BEFORE you deploy it.

What references are giving you troubles?

Remember that you must code (and use references) based on the "lowest common denominator" theory. Essentially that means that your development machine must use the "lowest" version of any item that will be used. For example, if you've referenced Outlook, then you need to determine what versions of Outlook are going to be used in your deployed environment, and be sure that your development machine is AT or BELOW that version. Access can upsize references, but it cannot downsize them.

You can also use Late Binding to avoid many of the reference versioning issues - but that still requires the target machine to have that reference installed and properly configured.