Results 1 to 10 of 10
  1. #1
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Secure front end running on diff Access Versions (

    I'd love a simple solution to this but I suspect there isn't one.
    I live in hope.

    I have several users using a FE BE access database.
    The system runs against a secure .mdw file which
    can reside either on the users PC, or the server.
    I prefer the latter but I am willing to be educated on this.

    The front as well as the back is secured against the same .mdw

    I get 2 major problems.
    One I think is an Access Problem.

    The database has No USERS GROUP permissions at all
    and the standard Admin is only a member of USERS to full security.

    There is an admins groups and some others.

    Problems....

    Some Users have Access 2003 and some have 2000

    All databases are in 2000 Format

    Anyone who is Admins can use the system fine

    1. On 2003 PC's if groups other than Admins try to use the system they get a message
    saying they cannot open the database.
    There are NO read permissions to table MsysAccessObjects.
    Can get round this by making sure that these users only have Access 2000

    2. If an administrator using say Access 2003 makes any changes to the security
    then all permissions are lost on the database, regardless of whether they
    are only loading up their local copy of the front end
    When this is done and then the permissions are looked at on a 2000 machine
    then the permissions are set to defaults and Users have full permissions.
    Everyone is a member of Users so suddenly everyone has full permissions.

    I appear to have three possible solutions but really need advice on this.

    1. Make everyone convert to 2000
    2. Make everyone convert to 2003
    3. ?? Have 2 .mdw file one for the 2003 machines and one for the 2000

    4. Someone else has a better idea.

    I have 4 days to try and resolve this so.....
    Before I go ahead and implement one of these solutions I would love some help.

    Thanks in advance (hopefully)....
    Andrew

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

    Re: Secure front end running on diff Access Versions (

    Has the secured .mdw file originally been created in an older version of Access (97 or earlier), or in Access 2000?

  3. #3
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Secure front end running on diff Access Versio

    It was done in 2000.

    I was aware of an issue between 97 and 2000,XP etc
    But naively assumed that since the native database format of 2000,XP and 2003 is 2000
    and since the database works fine in all 3 versions without the security element
    then there would not be a problem.
    But there was.

    I guess I could try re-building the MDW from Scratch.
    There are only 5 standard groups in Users and Admins
    and also only 12 users, so it would not be a major problem
    but I'd love to know why it gets converted.
    Andrew

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

    Re: Secure front end running on diff Access Versio

    There shouldn't be a problem mixing Access 2000, 2002 and 2003 using the 2000 format, but perhaps either the .mdw file or the database has become corrupt. Access 2003 is more sensitive to corruption than Access 2000. So forst, try re-creating the .mdw file from scratch, and if that doesn't help, import all database objects into a blank new Access 2000 format database.

  5. #5
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Secure front end running on diff Access Versio

    I'll give that a go and let you know how I get on.

    Interestingly, I have a machine here with BOTH 2000 and 2003 on.
    I tried it using a shortcut with both, and it keeps all security in place regardless of which
    version of Access I try to open it on, which is of course what I expected.

    I am now going to try it on a PC with Only 2000
    Then on a different PC with 2003 and see what happens.

    If it still does not work, I will revert to method above
    If it does, then maybe there is something about that 2003 PC
    that it happened on and poss a re-install might be in order.

    Whatever the outcome, I'll keep you posted.

    Thanks for info so far.
    Andrew

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

    Re: Secure front end running on diff Access Versio

    Something else you should look at is the ownership of both databases - it should not be Admin as that will always let Admin in if they know the right tricks. I suspect that you do have some sort of corruption as Hans suggested, so I would build empty databases in 2000 format for both FE and BE, and then import all the objects into the empty databases and relink the tables, but be sure to do it with an Admins group UserID, and not Admin. That will properly configure the ownership of the database.

    As to whether to use a FE located on the server or the workstation, we nearly always put them on the workstation, since you must take exclusive control to make any design changes in the FE - even a simple tweak to a form or report. With it on the workstation, we can change the development copy, deploy it to the server, and then copy it to the individual workstations at their convienence. Also note that you will far less problems with corruption with that configuration.
    Wendell

  7. #7
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Secure front end running on diff Access Versio

    Yes I reckon that is a good idea and will employ that technique for sure.

    Regarding FE and work station.

    I always put the FE on the work station.
    However, I was wondering whether to put the secure MDW file as a one copy on the server with the BE, or also put
    local copies of that on the client.

    I have been putting it on the server, but on reading up more on this it appears
    that I might be more sensible to also put it on the client, because if it too got corrupted it would be a pain to have to re-build yet again.

    I was just looking for a second opinion on this.

    Thanks for advice to date.
    Andrew

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

    Re: Secure front end running on diff Access Versio

    It's safest to give everybody a local copy of the secured .mdw - it's less probable to get corrupted, and if it does, it affects only one user.

  9. #9
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Secure front end running on diff Access Versio

    Thanks.

    I had moved to this conclusion, just wanted a confirmed opinion

    Andrew
    Andrew

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

    Re: Secure front end running on diff Access Versio

    We also nearly always do put the MDW file on the workstation as well - as Hans notes, it's much less likely to corrupt, and if it does, you simply copy the master to the workstation again. It can get to be a pain if you have significant changes in staff and a significant number of users - in those cases we use a deployment tool to do the copy process.
    Wendell

Posting Permissions

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