Open up encrypted FE with Command Prompt or Script not working (1 Viewer)

[NauticalGent]

Good morning folks!

Playing around this morning, I did a quick db with a password. I can open it from file explorer with no issues - a quick prompt for the password and I'm in. However, when I try to do it from the command prompt: "C:\Program Files\Microsoft Office\root\Office16\MSAccess.exe" "C:\Users\18048\OneDrive\Documents\PassWordTest.accdb" /pwd PassWord

I get this:

No problem, I'll just type in the password, right? Wrong!

According to Google and ChatGPT, this is a known behavior and both sources have offered solutions. Before I go down those rabbit holes, I figured I would ask others who may have ventured down this road before...

 

[theDBguy]

I could be wrong, but I thought that /pwd switch was for ULS. No?

Sent from phone...

Edit: Yup, I thought so.

Microsoft Access Command-Line Switches | DEVelopers HUT

Explaining the concept of command-line switches in the context of Microsoft Access databases and how to use them. I also present, a second, better approach!

www.devhut.net

 

[NauticalGent]

Found this on Colin's website:

Assuming he is right , I guess you can't use a password switch with newer versions.

p.s. ULS?

 

[NauticalGent]

p.s. ULS?

User Level Security - duh!

 

[NauticalGent]

So, what I was trying to do was set a password for the FE so that the users would have to use the application script (PowerShell) to open the FE. I have some savvy users who are going to their local copy and opening it up from there.

 

[theDBguy]

So, what I was trying to do was set a password for the FE so that the users would have to use the application script (PowerShell) to open the FE. I have some savvy users who are going to their local copy and opening it up from there.

If you're using PS, then you should be able to use an Access Application object to open the FE. I think. I'll have to search for some examples. I know it can be done with VBS though.

 

[NauticalGent]

I have the script and everything works great. Every user has a FE copy on their PC in a specified folder: C:\Users\UserID\WMT_HSV\mydb.accdb.

Everything is fine except when there is an update. The PS script copies a fresh copy of the FE. If they bypass the script, no new copy - I am trying to force them to use the Application Shortcut that runs the script

 

[theDBguy]

I have the script and everything works great. Every user has a FE copy on their PC in a specified folder: C:\Users\UserID\WMT_HSV\mydb.accdb.

Everything is fine except when there is an update. The PS script copies a fresh copy of the FE. If they bypass the script, no new copy - I am trying to force them to use the Application Shortcut that runs the script

One way to do that is to use the /cmd switch. When the FE opens, you can check the Command function if it returns what you're expecting. Otherwise, simply quit the application and tell them to use the script instead.

 

[NauticalGent]

That is one option I was thinking of as well, but thought it was a bit of a "kludge" so I abandoned it. But if the DBguy is doing it then it MUST be good! Thanks for your time!

 

[theDBguy]

That is one option I was thinking of as well, but thought it was a bit of a "kludge" so I abandoned it. But if the DBguy is doing it then it MUST be good! Thanks for your time!

LOL. Well, if I think of a more elegant solution, I will let you know. For example, you could also consider adding an empty table in the FE. When the app opens, check if this table is empty, if so, populate it with today's date, or something. If not, quit the application. Just a thought...

 

[Gasman]

I have the script and everything works great. Every user has a FE copy on their PC in a specified folder: C:\Users\UserID\WMT_HSV\mydb.accdb.

Everything is fine except when there is an update. The PS script copies a fresh copy of the FE. If they bypass the script, no new copy - I am trying to force them to use the Application Shortcut that runs the script

I used to use Bob larsens's update, and that handled it beautifully.

Free Access Tools | BTAB Development

FRONT-END AUTO-UPDATE ENABLING TOOL (Works for all versions 2000 and up) Microsoft Access Front-End Auto-Update Enabling Tool - allows you to quickly add auto-updating to your front-ends (PLEASE NOTE: This tool is primarily meant for networked users that have direct access to the backend...

btabdevelopment.com

There is also this version.

FBA DB Launcher - MS Access front-end deployment tool - ForestByteApps

ForestByteApps - A place for Microsoft Access code samples and utilities to make your life easier. Free Microsoft Access tools and sample VBA code

forestbyte.com