sa**********@gmail.com wrote:
Hello,
I have a front-end access db on a server share - the users should
COPY the db to their desktop - but we know how that goes. I've tried to
make it read only and have denied execute permissions on the
directory but it's still runs off the server - i just get the read only message
in access.
Does anyone have a solution? Why am I able to execute the db? Is a
temporary copy being created on the desktop computer? I've noticed
that a .ldb file is not being created - perhaps due to write
permissions being denied(but i'm not sure about this)
thanks
Sam
Would SysCmd(acSysCmdAccessDir) or Access.CurrentDb.Name begin with
something other than "C" if they open the front end on the server
share?
James A. Fortune
There is a special type of exception called a DBConcurrencyException
which derives from the base Exception class. Because the DataSet stores
the original and proposed values of each column in a row, it knows how
to compare the values to the database to look for concurrency issues
automatically. For example, assume that a user changes the value of the
firstname field from Lloyd to Lamar and submits the changes to the
database. The changes, which are stored in a DataSet, are passed on to
the database via the DataAdapter's Update method. Before the data is
actually saved, if the name in the database is no longer Lloyd but is
now Lorenzo, a DBConcurrencyException exception will be thrown. This
exception can be caught and handled appropriately in whatever way suits
your application's needs best (you could, for example, enforce a "last
in wins" rule, giving the user the option to cancel the changes,
override, or force the update anyway, or some other technique).
--
http://msdn.microsoft.com/msdnmag/is...s/default.aspx
Hint: Think Timestamps -- Jim Rand