laccdb file when started by automation

[pdanes]

I have a database that writes out an HTA file, executes the file and kills itself.

The HTA file does some work, then restarts the spawning database and kills itself.

Most of this works well - I use loops to monitor status of the file system and decide when I can go on to the next task. For instance, the very first thing the HTA does is watch for the disappearance of the laccdb file of the database that fired it off. When that disappears, it knows that the spawning database has fully finished closing and it is safe to go on to the next step.

The last task, restarting the spawning database, executes properly, but I put a final step into the HTA, of looking for the appearance of the laccdb file, to know that the original database has properly started up, and the HTA may go off to the happy hunting grounds, knowing that everything concluded successfully.

Unfortunately, that last step is failing, and watching the folder containing all this reveals that the laccdb file truly does not appear. I naturally spent the first few minutes thinking evil thoughts about Microsoft, but upon further review of the role of the laccbd file, it occurrs to me that this may be in the "feature not bug" category - that is, the laccdb file is created only when the database is manually opened by a user, and when it is spawned by another process, via automation, there is no 'user' and so there is no laccdb file.

Can anyone shed some light on this? I looked around, but found nothing about the laccdb file not appearing.

[June7]

What is the code to open db?

I tested programmatically opening db with FollowHyperlink and laccdb is created.

[pdanes]

What is the code to open db?

I tested programmatically opening db with FollowHyperlink and laccdb is created.

Here are the pertinent parts:

Dim sh
Const AktivniSlozka = "C:\Users\danespe\Desktop\LichTest\"
Set sh = CreateObject("wscript.shell")
sh.Run AktivniSlozka & "Lichen.accdb /excl", 1, False

[isladogs]

A lock file isn't created when an ACCDB is opened exclusively. Change the default open settings for that database by removing the /excl switch in your code.

[June7]

Tested your code. Works. Removing the switch does allow the laccdb.

[pdanes]

A lock file isn't created when an ACCDB is opened exclusively. Change the default open settings for that database by removing the /excl switch in your code.

All these years and I never knew that. I just copied that line from somewhere without investigating it. Thanks.

[isladogs]

You're welcome.
Its always seemed illogical to me that no lock file is created when opened exclusively.
How does Access know the file is already open to prevent others opening it subsequently.
No doubt something obvious that I'm unaware of.

[June7]

Some deep hidden table?

[isladogs]

No. Deep hidden tables are only used as attached tables for complex datatypes such as MVFs.
Possibly a database property.