Front-end database for users without full version?

[Guest]

I share a database from a shared folder on my computer, and I want to split
it into FE and BE. My question is, can I give a FE database to users who
only have Access Runtime on their machines rather than the full version?

A second question: I set up user-level security for this DB, and have opened
up the share permissions for the folder containing the database. However,
every other machine that opens the database will only open it "read-only." I
have checked, double-checked, triple-checked the share permissions for the
folder and all files within, and they are all wide open. Does anyone know
why this happens?

Much thanks in advance!!

 

[Joseph Meehan]

A Paid Observer wrote:
....

A second question: I set up user-level security for this DB, and have
opened up the share permissions for the folder containing the
database. However, every other machine that opens the database will
only open it "read-only." I have checked, double-checked,
triple-checked the share permissions for the folder and all files
within, and they are all wide open. Does anyone know why this
happens?

Check their copy of Access. It may be set to opening exclusively be
default.

 

[George Nicholson]

can I give a FE database to users who

only have Access Runtime on their machines rather than the full version?

Yes, but...

Runtime does not include all the functionality of the full retail version
and that needs to be taken into account by the developer (you) or anyone
using the FE may have problems.

http://msdn2.microsoft.com/en-us/library/aa167800(office.11).aspx
Basics for Building Microsoft Office Access 2003 Runtime-Based Solutions

While written for Access 2003, the general thrust of the article is
applicable to earlier versions (2000 & 2002) and probably 2007 as well. Pay
special attention to: a) the list of disabled features and b) the runtime
command-line switch which you can use to simulate what Runtime users will,
or will not, encounter when using your FE.

Does anyone know why this happens?

Well, if everyone is using a single-file db, any number of things could put
the db into exclusive mode (including doing anything that even hints at
changing the design/property of anything at all in the db). Once you split
the db and each user has their own FE, this problem might disappear. Until
then its sort of a moot point since Access was simply never intended to have
multiple users in a single-file mdb simultaneously, so any problems you
might be having could be chalked up to misuse. If the problems persist after
spliting, that's a whole different ballgame, but you have to take care of
the biggest issue first.


HTH,