[AccessD] 32->64 bit conversion

[Bill Benson]

Well, you could be right in your disbelief, maybe I am overstating the
effect of "distributing as ACCDE". By that all I know is that we take the
ACCDB and swap the last letter of the extension. Access treats the file as
an ACCDE and will not let the users near the code. We do not do anything in
particular to compile (and I wouldn't know how to uncompile) the tool
beyond what Debug | Compile does in the VBA IDE..

On Mon, Nov 1, 2021 at 2:34 AM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> I find that very hard to believe.
>
> There are no "conditional compilation constants" in an ACCDE file.  It
> only contains the cP
> code compiled from the text source code which is not present in an accde
>
>
> https://support.microsoft.com/en-us/office/hide-vba-code-from-users-ce6ab610-af07-4008-9
> 1e0-1ef1b796ff18
> <https://support.microsoft.com/en-us/office/hide-vba-code-from-users-ce6ab610-af07-4008-91e0-1ef1b796ff18>
> "Saving a database as an .accde file compiles all VBA code modules,
> removes all
> editable source code, and compacts the destination database."
>
>
>
> On 31 Oct 2021 at 23:22, Bill Benson wrote:
>
> > I am going to have to check that out because we distributed accde
> > versions to bank clients running both 2013 32 bit and 365 64 bit with
> > conditional compilation constants amidst api calls and have not had a
> > single customer service complaint in over a year.
> >
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>