Re: Access database

A I mentioned before, the number of work stations where a front end would be
required is many. It would not be feasible to manually visit each station to
install a front end. It would need to be a global install which I think would
require IT involvment. The back end currently resides on a network folder;
the permissions to the network folder are already established and allows for
the creation of an ldb file. The front end also currently resides in the same
folder. Only a limited number of individuals are able to navigate to this
drive/folder.

Perhaps I'm not fully understanding the .bat file, where it resides and how
it is activated.

Gwen

"Klatuu" wrote:

IT involvement should not be required.
But, this is a clue to an additional issue.
All users need to have read, write, and delete permissions on the network
folder where the backend mdb is placed. Without these rights, an ldb file
cannot be created and this will certainly result in locking issues in a multi
user environment.

If the proper rights are assigned, then all you need to do is put the master
copy of the front end in the folder with the back end where it can be copied.

If IT refuses to grant the rights described above, you will never have a
successful multi user implementation.
--
Dave Hargis, Microsoft Access MVP


"Gwen" wrote:

Thank you for your advice. I will need to speak to our IT department about
trying your suggestion. Hopefully they will be able to accommodate with
deploying a front end to each user and allowing the automatic front end
update. Thanks again.

Gwen

"Klatuu" wrote:

A different form will have no benefit here. You reall need to deploy a copy
of the front end to each user.
Managing version updates is not that difficult. There are automatic front
end updaters you can download (can't find a link right now or I would send
it), but it is also simple enought the create a .bat file that copies the mdb
from a specific network folder the the user's computer.

Here is an example of a .bat file for an application that is updated from
the network server every time it is loaded. In this case, it not only
ensures the user has the most current version, but there are several local
tables used in reporting that cause some bloat, so this keeps the file size
down without a compact/repair as well as keeping the version up to date:

Copy "O:\Installation\RealPro Install\Update MDE\*.*" "C:\Program
Files\RealPro\"
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\Program
Files\RealPro\REALPRO.mde" /runtime
--
Dave Hargis, Microsoft Access MVP


"Gwen" wrote:

The problem is the number of work stations that it would have to be installed
on, and also managing any design changes to the front end.
Would creating my own form to navigate through rather using the switchboard
manager be of benefit?

Gwen

"Douglas J. Steele" wrote:

Each user should have his/her own copy of the front-end, ideally on his/her
hard drive. Splitting the application into a front-end and back-end, but
sharing the front-end, really doesn't buy you anything.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Gwen" <Gwen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:430D036F-80E7-4EB7-A23D-174814993038@xxxxxxxxxxxxxxxx
The database is split, there is one front end accessed via a link on our
intranet as opposed to having a front end loaded on individual work
stations.
The actual drive the front end is located on is not visible/accessable to
the
end users.

Gwen

"NetworkTrade" wrote:

first point of resolution is to be sure that this is a split database and
that each user is operating their own individual front end application.

--
NTC


"Gwen" wrote:

I have a database that opens with a switchboard page. Clicking one of
the
controls takes you to another switchboard page where the controls open
forms
to enter or edit data. It is a multi user environment. I've been
encountering
a problem where some users click the control on the second page to open
a
form and the control appears to be pressed, but nothing happens (one
control
opens the form in add mode and another opens it in edit mode). This
occurs
intermittenly to different users at different times. At the same time
that
some users encounter this problem, other users do not.



.

Relevant Pages

  • Re: Access database
    ... The back end currently resides on a network folder; ... Perhaps I'm not fully understanding the .bat file, ... a problem where some users click the control on the second page to open ...
    (microsoft.public.access.forms)
  • Re: Access database
    ... All users need to have read, write, and delete permissions on the network ... Here is an example of a .bat file for an application that is updated from ... a problem where some users click the control on the second page to open ... opens the form in add mode and another opens it in edit mode). ...
    (microsoft.public.access.forms)
  • Re: Access database
    ... from a specific network folder the the user's computer. ... Here is an example of a .bat file for an application that is updated from ... a problem where some users click the control on the second page to open ... opens the form in add mode and another opens it in edit mode). ...
    (microsoft.public.access.forms)
  • User Rights
    ... I have a user who I have given FULL control rights to her network folder. ... She tells me she can not add permission for other folks to specific ... Client Domain: DOMAIN1 ...
    (microsoft.public.win2000.security)
  • Re: User Rights
    ... | I have a user who I have given FULL control rights to her network folder. ... I have propogated the FULL control to all her sub ... | Client Domain: DOMAIN1 ...
    (microsoft.public.win2000.security)