Is it a requirement to using the Access Runtime version that the database VBA source code be compiled? Or will the Access Runtime raise no issue operating an .accdb file format?
I don't think it matters either, and I've never used the "r" extension. Most of my users have the runtime version, and I've always distributed mde/accde files. I just tested an accdb on a PC with 2007 runtime and it ran it fine, though my testing was admittedly limited.
My understanding of the "r" extension was that it would force a computer with the full version of Access to run the file in runtime mode. If true, it would have no effect on a PC with only the runtime version installed.
I don't think it matters either, and I've never used the "r" extension. Most of my users have the runtime version, and I've always distributed mde/accde files.
And I mentioned testing an accdb on a PC with just the runtime and it worked fine. Renaming the file isn't accomplishing anything on a computer that only has the runtime installed.
Which is exactly what I was seeking. The solutions I develop for clients are open source solutions. The client's paid for my consulting time to develop a solution for them, not a lock-in black box.
Michael - it occurred to me.
I might still be inclined to use a .de rather than a .dr, for the distribution version - or at least discuss it with your client
It's one thing supplying code to the company for their use, but it may be another thing making the full code available to any of the users. Just a thought.