G
Guest
Following plenty of excellent advice in these forums I have finally developed
and launched my app at work. I split the database, putting the backend on the
server and the frontend on the user workstation as well as making my own mdw
file to stop unwanted visitors! I made a custom desktop shortcut pointing to
the location of MSACCESS.EXE, the mde fe file and the mdw file and this all
works great.
However, I'd really appreciate some advice from those with more experience
to deal with a problem that has occurred. I work in a hospital and my app is
for the doctors to enter unusual case presentations. Initially I'm just
working with one doctor whilst we test the programme. Every user in the
hospital has their own private area on one server and I have installed the FE
file in the doctors area of that server. The BE is installed on a separate
server for general access. My intention was that I could give him a desktop
icon that pointed to all the relevant files and then it wouldn't matter which
PC he was logged onto he would be able to access the programme. We have PC's
all over the hospital that can be used by any user. First question; does it
defeat the benefits of splitting a db if the FE is also on a server albeit a
different one from the BE? Hospital security doesn't allow installation of
files onto C: drives. My second question is that the location of the
MSACCESS.EXE file varies on many of the workstations because of
inconsistencies in the original installation of MS Office when the PC's were
first built, this is beyond my control. I have ended up having to put (so
far!!) 4 shortcuts on the desktop to cater for the 4 different locations on
the Access application. My doctor uses the shortcut that has a "proper" icon
depending upon which PC he has logged onto. Can anyone make any suggestions
for improvements on this?
Thanks for any suggestions you may have,
Ian.
and launched my app at work. I split the database, putting the backend on the
server and the frontend on the user workstation as well as making my own mdw
file to stop unwanted visitors! I made a custom desktop shortcut pointing to
the location of MSACCESS.EXE, the mde fe file and the mdw file and this all
works great.
However, I'd really appreciate some advice from those with more experience
to deal with a problem that has occurred. I work in a hospital and my app is
for the doctors to enter unusual case presentations. Initially I'm just
working with one doctor whilst we test the programme. Every user in the
hospital has their own private area on one server and I have installed the FE
file in the doctors area of that server. The BE is installed on a separate
server for general access. My intention was that I could give him a desktop
icon that pointed to all the relevant files and then it wouldn't matter which
PC he was logged onto he would be able to access the programme. We have PC's
all over the hospital that can be used by any user. First question; does it
defeat the benefits of splitting a db if the FE is also on a server albeit a
different one from the BE? Hospital security doesn't allow installation of
files onto C: drives. My second question is that the location of the
MSACCESS.EXE file varies on many of the workstations because of
inconsistencies in the original installation of MS Office when the PC's were
first built, this is beyond my control. I have ended up having to put (so
far!!) 4 shortcuts on the desktop to cater for the 4 different locations on
the Access application. My doctor uses the shortcut that has a "proper" icon
depending upon which PC he has logged onto. Can anyone make any suggestions
for improvements on this?
Thanks for any suggestions you may have,
Ian.