Results 1 to 8 of 8
  1. #1
    Join Date
    Aug 2009
    Posts
    4

    Unanswered: Security mdw issue

    Im running an Access 2003 application. We recently upgraded to Office 2007 (did not convert the files). Now I have 2 machines where the security log-in box doesnt appear and they just open the app as admin, I have 1 that works fine. Ive tried rejoining the workgroup file, de-joining and rejoining, etc.. to no avail.

    I feel it is a windows, or Access setting and not a DB issue but I can not figure out whats going on... any ideas????

  2. #2
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Is the MDW file included/referenced in the shortcut that launches the application?
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  3. #3
    Join Date
    Aug 2009
    Posts
    4
    Not sure what you mean about referenced by the shortcut. THe shortcut links to the mdb front end. The mdw file happens to sit in the same directory as the frontend and backend mdb files. Ive joined the Workgroup but Access seems to ignore it when I open the db... It was working before the upgrade and like I said we have a couple of machines that were upgraded that it still works on..

  4. #4
    Join Date
    Oct 2004
    Location
    Melbourne, Australia
    Posts
    201

    Access Security on Update

    The default .mdw file in MSAccess is System.mdw buried somewhere in the Program Files or Application Data areas. It is accessed by default because of an entry somewhere in the registry (I think). Your Access 2007 probably came with this assumption built in. Somehow, another .mdw file can become the default, though whether this happens automatically because of the removal of the System.mdw I am not sure(Windows is far too esoteric for this bear of little brain). However, as has been suggested, the command in the shortcut (or any other batch file) should include an explicit reference to the .mdw file that is to be used, if only to resolve this anomaly.

    The general format is:

    <path_to_MSAccess>\msaccess.exe <path_to_database\databasename.mdb /wrkgrp <path_to_workgroup>\workgroupname.mdw

    This can be followed by \user "username" \pwd "password" as you may see fit.

  5. #5
    Join Date
    Aug 2009
    Posts
    4
    It finally logged in properly once I added the username and pwd switches. Problem is.. why doesnt Access launch the log-in dialog at startup???
    Thx

  6. #6
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    probably because that instance of access is linked to a workgroup file which has a user name of admin with no password
    I'd rather be riding on the Tiger 800 or the Norton

  7. #7
    Join Date
    Aug 2009
    Posts
    4
    but I have joined a different workgroup file that does have users and passwords... I could buy that if I had not created a new WG file w/ users and not joined it...

  8. #8
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    ..but did you remove the user "admin", or at the very least set a password......
    I'd rather be riding on the Tiger 800 or the Norton

Posting Permissions

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