Results 1 to 12 of 12
  1. #1
    NickMDal is offline Novice
    Windows 7 64bit Access 2003
    Join Date
    Dec 2017
    Posts
    18

    Failure of fOSUserName() and endless conflict between Access 2003 and 2016

    Our business is very dependent on a complex Access 2003. We have not been able to upgrade the backend ever since Microsoft dropped replication support.


    We get two errors that often happen at the same time. Not sure if they're related.




    1. We get locked out of our app as fOSUserName() fails to obtain the Windows 7 logon userid. This resolves unpredictably after a Windows update or following an unknown event.


    2. Since updating to Office 365, we get the "reconfiguring office 2003" message on all machines after a reboot, when trying to open Access 2003. The desktop icons change to the Office 2016 icons. The automatic reconfigure usually works and the icons returned to 2003.


    This is a healthcare practice and these errors are exhausting. Today we have both. Any suggestions for a cause or solution?


    All machines...


    Access 2003
    Win7 64
    Office 365

  2. #2
    ranman256's Avatar
    ranman256 is offline VIP
    Windows Vista Access 2010 32bit
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    9,521
    I found no reason to upgrade from 2003.

    1. try sUserID = Environ("Username") , see if that get the ID.

  3. #3
    orange's Avatar
    orange is offline Moderator
    Windows 10 Access 2010 32bit
    Join Date
    Sep 2009
    Location
    Ottawa, Ontario, Canada; West Palm Beach FL
    Posts
    16,716

  4. #4
    isladogs's Avatar
    isladogs is offline MVP / VIP
    Windows 10 Access 2010 32bit
    Join Date
    Jan 2014
    Location
    Somerset, UK
    Posts
    5,954
    Having two versions of Access/Office will always cause these configuration issues.
    There is no real way of solving it other than removing one version.

    I also have a workstation with both Office 2010 and 2016.
    I do all development work in 2010 and only rarely use 2016 for testing apps.
    However, when I do swop, I also get the same issues
    Colin, Access MVP, Website, email
    The more I learn, the more I know I don't know. When I don't know, I keep quiet!
    If I don't know that I don't know, I don't know whether to answer

  5. #5
    NickMDal is offline Novice
    Windows 7 64bit Access 2003
    Join Date
    Dec 2017
    Posts
    18
    I am not the VB programmer so changing function is second resort.

    This was in the referenced fOSUnername() thread.

    I had the same issue and discovered that there is nothing wrong with the code but with a setting by default in Access 2010 in the Trust Center - DEP Settings - Enable Data Execution Prevention mode. Unchecking this box will allow the code to run properly using the api in a standard module.
    Does this DEP setting apply to Access 2003 with Office 365 installed? DEP Settings is not in the Office 365 options section. In Access 2003, security is low and "trust access to VB project" is greyed out.

  6. #6
    NickMDal is offline Novice
    Windows 7 64bit Access 2003
    Join Date
    Dec 2017
    Posts
    18
    Quote Originally Posted by ridders52 View Post
    Having two versions of Access/Office will always cause these configuration issues.
    There is no real way of solving it other than removing one version.
    We don't use or need Access 2016. We do not have the option to remove it. It is forced with this version of Office 365. I'd be happy to uninstall it.

  7. #7
    NickMDal is offline Novice
    Windows 7 64bit Access 2003
    Join Date
    Dec 2017
    Posts
    18
    Quote Originally Posted by ranman256 View Post
    I found no reason to upgrade from 2003.

    1. try sUserID = Environ("Username") , see if that get the ID.

    Thanks for your suggestion. May I ask, how would I adjust the sub below to use sUserID? I have almost no coding skills but can compile and test it.

    Private Sub Form_Load()
    Me!txtName = fOSUserName()
    If (fOSUserName() = "USER1" Or fOSUserName() = "USER2" Or fOSUserName() = "USER3") Then
    CmdLogon.Enabled = True
    Else
    CmdLogon.Enabled = False
    End If
    End Sub

  8. #8
    ranman256's Avatar
    ranman256 is offline VIP
    Windows Vista Access 2010 32bit
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    9,521
    instead of coding, put the users in a table with a LEVEL field.
    the code in the LEVEL allows that user rights.
    so instead of
    IF USER = A OR USER = B,...etc

    just lookup their code and enable.
    Code:
    sUser = Environ("Username")
    sLevel = Dlookup("[Level]","tUsers","[userid]='" & sUser & "'") 
    CmdLogon.Enabled = sLevel = "A"

  9. #9
    isladogs's Avatar
    isladogs is offline MVP / VIP
    Windows 10 Access 2010 32bit
    Join Date
    Jan 2014
    Location
    Somerset, UK
    Posts
    5,954
    Quote Originally Posted by NickMDal View Post
    We don't use or need Access 2016. We do not have the option to remove it. It is forced with this version of Office 365. I'd be happy to uninstall it.
    OK but if nobody uses A2016, you won't get the configuration issues.
    So clearly people are using it as you do have the issues
    Colin, Access MVP, Website, email
    The more I learn, the more I know I don't know. When I don't know, I keep quiet!
    If I don't know that I don't know, I don't know whether to answer

  10. #10
    NickMDal is offline Novice
    Windows 7 64bit Access 2003
    Join Date
    Dec 2017
    Posts
    18
    Thanks for helping but not sure if I understand. I don't use A2016. Its just on all of the machines and interferes with 2003. 16 being there (maybe with office updates or something) just keeps trying to be the default Access version against our will.

  11. #11
    isladogs's Avatar
    isladogs is offline MVP / VIP
    Windows 10 Access 2010 32bit
    Join Date
    Jan 2014
    Location
    Somerset, UK
    Posts
    5,954
    You're right about updates.
    Every time Office 2016 is updated it will reconfigure the registry to set that as the default.
    However, at most, that should occur once each month

    There's absolutely nothing you can do about it if you aren't allowed to remove 2016....other than accepting defeat and swopping over to 2016.
    Colin, Access MVP, Website, email
    The more I learn, the more I know I don't know. When I don't know, I keep quiet!
    If I don't know that I don't know, I don't know whether to answer

  12. #12
    NickMDal is offline Novice
    Windows 7 64bit Access 2003
    Join Date
    Dec 2017
    Posts
    18
    Quote Originally Posted by ridders52 View Post
    There's absolutely nothing you can do about it if you aren't allowed to remove 2016....other than accepting defeat and swopping over to 2016.
    We are dependent on replication and so cannot convert. It unfortunately has been essential for our business and has been utterly reliable.

    We do not have the option to convert to 2016. Replication was dropped since the 2007 version supported. Also our DB is also very complex with 126 forms. Conversion from 03 would not be practical and probably not possible.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Running Access 2003 with Office 2016
    By NickMDal in forum Access
    Replies: 4
    Last Post: 12-28-2017, 08:56 PM
  2. Update DB from 2003 to 2016
    By Rigodude in forum Access
    Replies: 4
    Last Post: 02-08-2017, 05:43 PM
  3. Access 2016 - Method AccessConnection failure
    By andrea76 in forum Programming
    Replies: 2
    Last Post: 01-30-2017, 08:06 AM
  4. Restrict Access to Form Based on fOSUserName()
    By ricker090 in forum Programming
    Replies: 1
    Last Post: 11-28-2012, 04:07 PM
  5. Write conflict - Access 2003
    By mafrank101 in forum Access
    Replies: 7
    Last Post: 10-10-2012, 07:44 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums