MS Access Database (MDB) "read only" problem

[wxperson99]

HI,

I have a problem that seems very odd and hope someone (tech support?) has a solution. I have spent quite a bit of time diagnosing and recreating the issue.

Here are the facts.

1. I have a Native Engine install that among other things installs MS Access MDB databases (i.e. user.mdb).
i.e. Install Files D:\build\build2016\global\Database\user\userdb.mdb to $TARGETDIR$\Database\user

2. If I build the install as uncompressed (CD/DVD) the installation works fine with NO issues.

3. If I build the install as a single file (with minimal compression selected.. the 2nd tick mark)... the installation appears to work find EXCEPT that my MS ACCESS files as installed (target) have READ ONLY permission. Even though the source files are not READ only. This causes application problems.

4. As an aside... If change the NATIVE ENGINE to FALSE (MSI)... and install as a single file... the issue described in #3 above does not occur. All is fine.

I would like to know why #3 is occurring and how to fix it. There should be a way to have a single file installation in Native Engine mode without having the MS ACCESS (MDB) files having their access change to READ ONLY.

Thanks for any help.

George

[FrancescoT]

Dear George,

which IA version are you using?

Do you have any chance to send me a very minimal project that replicates the issue?

Regards

[wxperson99]

I am using Installaware studio X3.

Reminder: This only occurs with the NATIVE_ENGINE set to true.

The project is fairly large but I can tell you that anytime the install is built using compression... such as the single file or the web deploy... this "READ ONLY" problem occurs with MS ACCESS (MDB) databases.

IT does NOT occur when I choose DVD/CD build

That, to me, indicates some kind of "bug" in the product. It should not treat the DVD/CD build differently than the single file or web deploy build.

Again... this only occur with the NATIVE_ENGINE on.

FYI... the database files are being copied using the following (copied) command.

~InstallAware Clipboard Data~
~Install Files~
~{AD703551-9F7E-4589-BE20-C98626954AB9}~
~D:\build\build2016\global\database\systemdb.mdb~
~FALSE|~
~$TARGETDIR$\Database~
~FALSE~
~FALSE~
~FALSE~
~FALSE~
~FALSE~
~FALSE~
~FALSE~
~FALSE~
~FALSE~

Hopefully this information points to where the problem is with IA.

Thanks,

George

[FrancescoT]

Dear George,

I didn't asked for your real project. I asked you for a minimal one that replicates the issue ... you may release a dummy project from scratch that just tries to install your DB file.

Anyway I am not excluding a possible issue and honestly, I never tried to install MS Access db file.

At any rate, did you try to force the Write/Read permission over that file (once installed) via the "Set Access Control" command?
This may be a workaround to try.

Regards

[wxperson99]

I will try the workaround...

Is this the correct format?

~InstallAware Clipboard Data~
~Set Access Control~
~{5DB61301-3AFE-4337-8852-6656F6334DAF}~
~$TARGETDIR$\Database\places.mdb~
~TRUE~
~FALSE~
~FALSE~
~FALSE~
~~
~FALSE~
~FALSE~
~FALSE~
~FALSE~
~TRUE~
~TRUE~
~FALSE~
~FALSE~
~FALSE~
~FALSE~

George

Any idea of why it would act differently when the install is compressed than when it is not.

[wxperson99]

The Set Access Control command seems to be a workaround.

I would still like to know why the install acts differently when compiled/compressed as opposed to the DVD/CD build.

Thx,

George