Deploying a split database

[DNewman]

I am attempting to deploy a split Access 2010 database to an XP PC with service pack 3.(NOT by choice!)
There is no Access on the XP machine so this would be a Run-Only version.
MS claim this will work.
I was hoping to deploy both the front-end and back-end with a single package. Is this possible?
Does the back-end have to be a run-only Database as well as the front-end?
Is it possible to save a database as run-only in Access 2010? (I was hoping to copy upgrades onto the XP machine without having to re-deploy it all)

 

[pbaldy]

You don't really "save a database as run only". What you do is install the runtime version of Access on the PC, and it will run your database. The runtime version has no design capability. Most of us would distribute an mde/accde as well, but I wanted to point out the distinction.

 

[DNewman]

Many thanks, my misconception cleared - as you might guess I am only just getting into 'deploying' (after a an abortive attempt long ago with Access2000!)
My front-end starts up by looking for its back-end and if it can't find it allows the used to locate it and it then unlinks/relinks the tables.
Will this still work if I convert the front end to .accde?

 

[pbaldy]

It should; I've got relinking routines running in accde's.

 

[gemma-the-husky]

you will need code to link the databases, I think. With the run time you don't get all the support utilities, and I don't think you will be able to manually connect the tables

you also don't get all the menus/ribbons either - so you have to programme all the "special" facilities you need. Also ANY run time error will just crash the database

you can simulate exactly what you will see, by renaming your database with .mdr/.accdr suffix. As in all such cases, keep a safe copy of your latest dbs version. This will enable you to test the implementation.

 

[gemma-the-husky]

just a thought. A2010 may require W7, not WXP. Not sure without checking.