Open MS-Access encrypted database in Runtime version with UserControl false

Question

I work with Access runtime version and I need to open an encrypted database .accdb. I created a dummy file to work with getobject and opencurrentdatabase statement. I can't work with CreateObject("Access.Application") or new access.application because this is the runtime version.

My code is this, and works fine but when I open the encrypted database the UserControl property is false, and it opens whith any access message like docm.setwarnings in false and "docm.setwarnings true" doesn't work.

Dim appRT As Object

Public Sub OpenEncryptDb()
Const Q As String = """"

strPathEncryptDb = CurrentProject.Path & "\encryptdb.accdb"
strPathToDummy2 = CurrentProject.Path & "\dummy.accdb"
strPathToRuntime = SysCmd(acSysCmdAccessDir) & "msaccess.exe"

Shell Q & strPathToRuntime & Q & " /RUNTIME " & Q & strPathToDummy2 & Q, vbNormalFocus

Set appRT = GetObject(strPathToDummy2)
With appRT
    .CloseCurrentDatabase
    .OpenCurrentDatabase strPathEncryptDb, False, "123456" 'open encrypt database
    .DoCmd.RunCommand acCmdAppMaximize
End With
End Sub

I shared the code in this link

https://1drv.ms/u/s!AsgXxStf7QGagQZIk8hcJShbCIye

open  first the master.accdb file. Note that when you open the final file "encryptdb.accdb", you can delete rows and you don't receive any  confirmation message that regularly you receive when you delete rows in MS-Access like "master.accdb"

Answer 1

Thank you for your answer,

Execute Shell() with the /runtime switch and full ms-access version is equal that execute shell() with only ms-access runtime version installed in the pc. If you have ms-access full version installed the final database works fine without /runtime switch, because it make an object of ms-access.

When you install only ms-access runtime version in your machine, without full version of ms-access, you receive same error  without /runtime switch in Shell().

Answer 2

I had lost track of this question while waiting for the clarification I asked for, but I finally had a chance to look at the posted databases.

The problem seems to be caused by the /runtime switch, or runtime mode itself.  I find that if I remove that switch from the command-line that is executed via Shell(), the secondary database works as expected, with the normal warnings being displayed.  The .UserControl property can't be set, but it turns out that's okay because the second instance of Access isn't created by automation, so .UserControl is already True.

I tried to find a way to make it work properly while specifying the /runtime switch, but was unable to do so.  I don't have the Access runtime installed, so I can't swear that its behavior under the runtime module would be the same as when the /runtime command-line switch is specified; of course, it's supposed to be, but I can't test that.

Answer 3

excuse me some else linked it in  another thread, i edit the original question

Answer 4

We prefer that you not piggyback your question on someone else's thread. So your question was split from the older thread you posted to. Please provide the code you are using and a fuller explanation of the problem so we can help.

Please note that an accdr file is meant to run as if it was being run using the Runtime version of Access. Therefore, design elements are not accessible.

Answer 5

I'm sorry, but I don't understand your question.  Could you please ask it again with different phrasing?