Results 1 to 14 of 14
  1. #1
    2 Star Lounger
    Join Date
    Nov 2004
    Location
    London, United Kingdom
    Posts
    152
    Thanks
    0
    Thanked 0 Times in 0 Posts

    front end on c drive (Access 2000)

    I was wondering if any one could advise me, or point me in the way of a relevant link.

    I have a database with about 20 users. It is currently on a shared drive. I was however thinking of splitting the database. But I am not sure whether to load the front end on to each pc or if it should stay on the network. Will my application be too slow if everyone opens the same front end file? Isn't there a lot of maintainance to be done if the front end has to be copied to each pc each time there is a change to the application design?

    Many thanks

    Amanda

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: front end on c drive (Access 2000)

    The general recommendation is to give each user an individual copy of the frontend.

    If you don't allow users to create their own database objects (queries etc.) in the frontend, you only have to give them a new copy if you have modified the design of the frontend, it can overwrite the old version. If you do allow users to create their own database objects, and if you want to let them keep those, updateing becomes more complicated. There are tools to help with this, such as DBLauncher from <!profile=WendellB>WendellB<!/profile>.

  3. #3
    2 Star Lounger
    Join Date
    Nov 2004
    Location
    London, United Kingdom
    Posts
    152
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: front end on c drive (Access 2000)

    Thanks Hans

    So is the idea to write a batch file that copies the latest version of the front end each time the user switches on?

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: front end on c drive (Access 2000)

    That is a possibility, but it's not always necessary. Depends on the situation.

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: front end on c drive (Access 2000)

    The front ends should contain forms, reports, queries, and code modules, plus any local tables that are appropriate. The back end contains the data tables. There are links to these tables in the front ends. The only reason for copying a new front end is to distribute changes in that front end to the users. If you aren't changing the forms, etc., there is no need to give them a new front end.
    Charlotte

  6. #6
    2 Star Lounger
    Join Date
    Nov 2004
    Location
    London, United Kingdom
    Posts
    152
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: front end on c drive (Access 2000)

    There will be lots of changes to the front end.

  7. #7
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: front end on c drive (Access 2000)

    What sort of changes? You were talking about 20 users and splitting the database, so that sounded like you had completed the design. And are these users all on it at once? If not, you might want to split the database but leave both front and back end on the server until you complete the changes, the distribute the front end to local PCs.
    Charlotte

  8. #8
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: front end on c drive (Access 2000)

    >>So is the idea to write a batch file that copies the latest version of the front end each time the user switches on? <<

    That's what I do. I stick a link to this batch file in each user's Startup folder, so it executes whenever they reboot.

    I've seen other solutions in which there is code within the DB that checks for a more recent version of the FE, and then will download the new version at that time. As you get more users, this method becomes more manageable than the other method.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  9. #9
    2 Star Lounger
    Join Date
    Nov 2004
    Location
    London, United Kingdom
    Posts
    152
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: front end on c drive (Access 2000)

    that's great thanks.

    So if i create a batch file something along the lines of
    copy s:mismis.mdb "cocuments and SettingsAll UsersStart MenuPrograms"
    and then save the file in
    ocuments and SettingsAll UsersStart MenuProgramsstartup it will run automatically each time the pc is switched on?

  10. #10
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: front end on c drive (Access 2000)

    In addition to all the other responses you have received, you might find the background in our Database Splitting Tutorial useful. I should also note that http://www.fmsinc.com also has a tool called Total Access Startup available for handling the distribution of development changes.
    Wendell

  11. #11
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: front end on c drive (Access 2000)

    You can actually put the .bat file anywhere and just put a shortcut in the startup folder. I put it on the server, but I know every workstation is executing the FE out of the same directory, so they can all use the same .bat file.

    BTW, I'd get out of the habit of using mapped drive letters (like S<img src=/S/smile.gif border=0 alt=smile width=15 height=15>. Use the UNC designation, which includes the server name and shared directory name. So it might be something like:
    copy "serversharedfilesmismis.mdb" "c:Program FilesMISmis.mdb" or whatever.

    And I'd similarly use the UNC when linking. If manually linking, select the Network Neighborhood instead of the mapped drive.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  12. #12
    2 Star Lounger
    Join Date
    Nov 2004
    Location
    London, United Kingdom
    Posts
    152
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: front end on c drive (Access 2000)

    Thanks Mark,

    That has been a great help. I will take your mapping advice on board. I did look at the links too. I know now that I am definately doing the right thing splitting the database. I've only done it before when using sql server as the BE.

    Amanda

  13. #13
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: front end on c drive (Access 2000)

    You are ABSOLUTELY doing the right thing by splitting the database, no question about it. I create all new databases from scratch with a separate FE and BE.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  14. #14
    2 Star Lounger
    Join Date
    Nov 2004
    Location
    London, United Kingdom
    Posts
    152
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: front end on c drive (Access 2000)

    Yeah, thanks.

    Now that I've done it (and it's working perfectly) it all makes good sense. Can't believe I put it off for so long!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •