Disconect linked tables opened in front end from back end with vba executed from be

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • NeoPa
    Recognized Expert Moderator MVP
    • Oct 2006
    • 32633

    #16
    It seems like you now have as good (or better even) a handle on this than I do. I don't play too much in this area, but I hope you now have what you need to decide how to play it for your situation.

    Best of luck and Welcome to Bytes!

    Comment

    • puppydogbuddy
      Recognized Expert Top Contributor
      • May 2007
      • 1923

      #17
      Originally posted by FishVal
      @PDB



      Does that mean "Passive shutdown" - like setting "Jet OLEDB:Connectio n Control" property?
      Or it allows to logout user already logged in?

      Regards,
      Fish
      Hi Fish,
      With all the messages going back and forth, I did not see your question until now.....sorry.

      The truth is I don't know for sure, but I believe it would be passive shutdown because it seems to address preventing users from logging on. I provided the link on the basis of Tony Toews reputation (Access MVP,etc).....I have not personally used his Auto FE Updater.

      Just curious....What is the final outcome of this thread? Is using/testing the Auto FE Updater a problem, particularly if the system is backed up first?

      Comment

      • ADezii
        Recognized Expert Expert
        • Apr 2006
        • 8834

        #18
        The way I see it is that the FE Updater is primarily a Versioning mechanism whereby Users will always have the latest version whenever a new one is rolled out. This will guarantee a consistent and Up-to-Date Front End to the user. Locking out Users is not the Primary Function.

        Comment

        • puppydogbuddy
          Recognized Expert Top Contributor
          • May 2007
          • 1923

          #19
          Originally posted by ADezii
          The way I see it is that the FE Updater is primarily a Versioning mechanism whereby Users will always have the latest version whenever a new one is rolled out. This will guarantee a consistent and Up-to-Date Front End to the user. Locking out Users is not the Primary Function.
          Hi ADezii,

          I agree with you that Locking Out Users is not the primary function, but it might be more robust than what appears at first glance......but unless we hear from somebody who has used it, we will probably never know for sure.

          To see what I mean, click on the hyperlink I provided and go to the bottom of the page that comes up. There you will see more hyperlinks for more details. Click on the hyperlink named "the Utility", you will see a form and the following statement (excepted):

          "If you run the utility interactively, by clicking on the StartMDB.exe from within Windows Explorer you will see an interactive form, similar to the form above, where you can validate the INI file, select the shortcut icon file and lockout or un-lockout users from your app."

          Comment

          Working...