I have an MDB with tables secured by an MDW. Management decrees that it cannot migrate to SQL Server any time soon. In the meantime, I must build an Access frontend to provide a user interface.
I could build the frontend as an MDB, and then compile it to MDE. I would rather build it as an ACCDB, and then compile it to ACCDE, in anticipation of swapping out the MDB backend, for a SQL Server backend, down the road.
To do that, however, I would need to create links in an ACCDB/ACCDE frontend to secured tables in an MDB backend.
I am able to open an ACCDB through a shortcut whose "/wrkgrp" switch points to the MDW that secures the MDB. This forces a logon, through the MDW, to open the ACCDB.
If the user has Open/Read permission for the MDB, and Read Design permission for its tables, then they can link to them from the ACCDB. They also can read, update, insert, and/or delete MDB data through ACCDB links, depending on how I set table permissions in the MDB.
Conversely, if I open the ACCDB without a shortcut through the MDW, then no logon occurs, and I cannot access MDB data through ACCDB links.
(Compiling the ACCDB results in an ACCDE that behaves identically in all of these respects.)
This seems to achieve my goal, but I cannot find documentation to support this approach. Am I starting down a path with known dangers, or is this common and acceptable practice?