Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Db file on a Server

Discussion in 'Information Technology' started by Ian, Jul 28, 2006.

Tags:
  1. Ian

    Ian
    Expand Collapse
    Guest

    I have developed a db file (.mde) for use in my hospital. The .mde file will
    reside on a publicly available server so all employees in the hospital can
    access the file. The expected number of users in total maybe around 50 but
    probably no more than 10 at any one time.

    I have not deployed an .mde file like this before and would really welcome
    any suggestions of issues I need to be aware of when there are going to be
    more than one person with the db open at any one time. Does Access block one
    user from adding records if another is already doing the same automatically
    or do I need to make preparations myself.

    Thanks for your comments,
    Ian.
     
  2. Loading...

    Similar Threads Forum Date
    Sikh News Profiled US Sikh Throws 'Know Me' Challenge Breaking News Jul 25, 2016
    Hard Talk Sikh Musician Racially Profiled At US Restaurant Hard Talk Jul 6, 2016
    India Patna man files defamation suit against son for inter-caste marriage Breaking News Jan 6, 2014
    USA Federal hate crime indictment filed in 'savage' attack on cab driver Breaking News Apr 4, 2013
    Malaysia Bank Islam Files Police Reports Against Chief Economist Breaking News Jan 23, 2013

  3. Albert D.Kallal

    Albert D.Kallal
    Expand Collapse
    Guest

  4. Ian

    Ian
    Expand Collapse
    Guest

    Hi Albert,

    Thanks for your reply, I had wondered about splitting the database and your
    link is very helpful. However, just one question, I was wondering why I need
    to install the mde on each users PC. The hospital server is readily
    accessible to all employees as a mapped drive (eg: H:\...), I was planning to
    install it here and merely have a shortcut to the mde on each users desktop.
    Is this wrong do you think?

    Many thanks,
    Ian.

    "Albert D.Kallal" wrote:

    > Ms access is multi user ready.
    >
    > However, do be aware that you need to install the mde on EACH computer. This
    > thus suggests that you have a split database.
    >
    > I explain in detail, how, and why you must do this here:
    >
    > http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
    >
    > --
    > Albert D. Kallal (Access MVP)
    > Edmonton, Alberta Canada
    > pleaseNOOSpamKallal@msn.com
    > http://www.members.shaw.ca/AlbertKallal
    >
    >
    >
     
  5. Tom Wickerath

    Tom Wickerath
    Expand Collapse
    Guest

    Hi Ian,

    Saving a front-end on a file share will result in unnecessary network
    traffic, to transfer all the bytes of information required to define each
    query, form, report, etc., as Albert explains in his article. It is much
    better to have a copy of the front-end installed locally, on each users hard
    drive. In addition, you really do not want to share a common front-end file,
    so if you really want to place the FE on a file server, you should point each
    user to their own copy.

    Here is a paper that should be helpful for you:

    Implementing a Successful Multiuser Access/JET Application
    http://www.access.qbuilt.com/html/multiuser_applications.html


    Tom Wickerath
    Microsoft Access MVP

    http://www.access.qbuilt.com/html/expert_contributors.html
    http://www.access.qbuilt.com/html/search.html
    __________________________________________

    "Ian" wrote:

    > Hi Albert,
    >
    > Thanks for your reply, I had wondered about splitting the database and your
    > link is very helpful. However, just one question, I was wondering why I need
    > to install the mde on each users PC. The hospital server is readily
    > accessible to all employees as a mapped drive (eg: H:\...), I was planning to
    > install it here and merely have a shortcut to the mde on each users desktop.
    > Is this wrong do you think?
    >
    > Many thanks,
    > Ian.
     
  6. Ian

    Ian
    Expand Collapse
    Guest

    Hi Tom,

    Thanks very much for the advice, it is much appreciated. I replied to Albert
    as I wasn't sure if I had been clear in my intentions and also being very
    green when it comes to deploying across a network. You have both made it
    clear for me how I need to proceed and both of you have provided extremely
    comprehensive documentation. For that I am extremely grateful and thank you
    both again for your help,

    Regards,
    Ian.

    "Tom Wickerath" wrote:

    > Hi Ian,
    >
    > Saving a front-end on a file share will result in unnecessary network
    > traffic, to transfer all the bytes of information required to define each
    > query, form, report, etc., as Albert explains in his article. It is much
    > better to have a copy of the front-end installed locally, on each users hard
    > drive. In addition, you really do not want to share a common front-end file,
    > so if you really want to place the FE on a file server, you should point each
    > user to their own copy.
    >
    > Here is a paper that should be helpful for you:
    >
    > Implementing a Successful Multiuser Access/JET Application
    > http://www.access.qbuilt.com/html/multiuser_applications.html
    >
    >
    > Tom Wickerath
    > Microsoft Access MVP
    >
    > http://www.access.qbuilt.com/html/expert_contributors.html
    > http://www.access.qbuilt.com/html/search.html
    > __________________________________________
    >
    > "Ian" wrote:
    >
    > > Hi Albert,
    > >
    > > Thanks for your reply, I had wondered about splitting the database and your
    > > link is very helpful. However, just one question, I was wondering why I need
    > > to install the mde on each users PC. The hospital server is readily
    > > accessible to all employees as a mapped drive (eg: H:\...), I was planning to
    > > install it here and merely have a shortcut to the mde on each users desktop.
    > > Is this wrong do you think?
    > >
    > > Many thanks,
    > > Ian.
     
  7. Tom Wickerath

    Tom Wickerath
    Expand Collapse
    Guest

    Hi Ian,

    You're very welcome. Good luck with your project!


    Tom Wickerath
    Microsoft Access MVP

    http://www.access.qbuilt.com/html/expert_contributors.html
    http://www.access.qbuilt.com/html/search.html
    __________________________________________


    "Ian" wrote:

    > Hi Tom,
    >
    > Thanks very much for the advice, it is much appreciated. I replied to Albert
    > as I wasn't sure if I had been clear in my intentions and also being very
    > green when it comes to deploying across a network. You have both made it
    > clear for me how I need to proceed and both of you have provided extremely
    > comprehensive documentation. For that I am extremely grateful and thank you
    > both again for your help,
    >
    > Regards,
    > Ian.
    >
    > "Tom Wickerath" wrote:
    >
    > > Hi Ian,
    > >
    > > Saving a front-end on a file share will result in unnecessary network
    > > traffic, to transfer all the bytes of information required to define each
    > > query, form, report, etc., as Albert explains in his article. It is much
    > > better to have a copy of the front-end installed locally, on each users hard
    > > drive. In addition, you really do not want to share a common front-end file,
    > > so if you really want to place the FE on a file server, you should point each
    > > user to their own copy.
    > >
    > > Here is a paper that should be helpful for you:
    > >
    > > Implementing a Successful Multiuser Access/JET Application
    > > http://www.access.qbuilt.com/html/multiuser_applications.html
    > >
    > >
    > > Tom Wickerath
    > > Microsoft Access MVP
    > >
    > > http://www.access.qbuilt.com/html/expert_contributors.html
    > > http://www.access.qbuilt.com/html/search.html
    > > __________________________________________
    > >
    > > "Ian" wrote:
    > >
    > > > Hi Albert,
    > > >
    > > > Thanks for your reply, I had wondered about splitting the database and your
    > > > link is very helpful. However, just one question, I was wondering why I need
    > > > to install the mde on each users PC. The hospital server is readily
    > > > accessible to all employees as a mapped drive (eg: H:\...), I was planning to
    > > > install it here and merely have a shortcut to the mde on each users desktop.
    > > > Is this wrong do you think?
    > > >
    > > > Many thanks,
    > > > Ian.
     

Share This Page