You can set up a replication set and designated design master to accomplish this. Search the Access Help to find out more.
However, replication in Access is not all that it is cracked up to be and most people find simpler methods such as redwoodly's.
We developed a menu system for users to...
Just one point here: never distribute or use an MDB in production, always create an MDE for end users to use. This is both a basic security principle and an operational advantage: the MDE is always named the same but each version of the MDB is named with a version number to control development.
What you have here is a typical Hierarchical Data problem and there are 2 established solutions to this: The Adjacency List Model and The Nested Set Model. Here are 2 articles that fully explain these models and provide you with all of the queries you need to implement them...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.