You can use Osage Inside Access on any number of MDBs on a single machine.  Each MDB will store the three files that Osage Inside Access needs.  But if you want some of these apps to contain links and not the actual tables, (perhaps in order to reduce the size of those MDBs), then here is how to do that

If only one MDB needs to do Remote Linking

• This assumes the three work tables have been created by starting up Osage Inside Access.
• Create a new MDB, call it something like:  IA_Data.MDB
• Open IA_Data.MDB, and import the three tables:  
• zIA_OsageInsideAccess, zIA_OsageInsideAccessChildren, and zIA_Prefs.  
• Critical:  Be sure to select the additional options, and specify to import Relationships (or you will have to recreate the relationship).
• Back in the original app, delete the three zIA tables, and then create links to them in IA_Data.MDB
• That does it!  Osage Inside Access will use the linked tables from now on, in this MDB.

If more than one application needs to do Remote Linking

• The instructions are exactly the same as above, except in IA_Data.MDB, give each set of three tables a unique suffix.  Then in the linking MDB, use the original name.  For example:
• Assume you have 2 MDBs to be linked this way:  App1.MDB, App2.,MDB.  
• Then, the table names in zIA_Data.MDB would be:
• App1_zIA_OsageInsideAccess, App1_zIA_OsageInsideAccessChildren, App1_zIA_Prefs
• App2_zIA_OsageInsideAccess, App2_zIA_OsageInsideAccessChildren, App2_zIA_Prefs
• In the linking applications (e.g. App1.MDB), create the three links, then remove the "App1" suffix from the link name, so that the names look exactly as Osage Inside Access is expecting.  Namely:
• zIA_OsageInsideAccess, zIA_OsageInsideAccessChildren, and zIA_Prefs.  

Here is a graphic picture of the situation: