I haven't attempted to do this yet but I was wondering. I have DB1 which has a table dedicated to days off for soldiers. I want to link DB2 to that table in DB1 so that I can make a calendar in DB2 for users to see when people are off and for how long. If I go to the external data tab and select access database and choose the table i want from DB1, is that a 1 time pull or will it be constant?
database connect to another database
- Thread starter Valentine
- Start date
- Local time
- Today, 13:24
- Joined
- Oct 29, 2018
- Messages
- 22,714
Be careful. It sounds like you simply want users of DB2 to only "see" that information from DB1. However, when you link a table, it is a "live" connection, which means you can view that data and also able to change it.
bastanu
AWF VIP
- Local time
- Today, 13:24
- Joined
- Apr 13, 2010
- Messages
- 1,406
You should consider having one "back-end" file to host the table(s) and two front-ends linked to it for the two separate functionalities (or only one that dynamically chooses what forms to show depending on the current user).
Cheers,
Cheers,
LarryE
Well-known member
- Local time
- Today, 13:24
- Joined
- Aug 18, 2021
- Messages
- 1,065
If you want users to just be able to see the data field but not be able to change it, then just set the field control Locked property to 'Yes' on all the forms or reports that have that field. It won't matter where the data field came from.
Cotswold
Well-known member
- Local time
- Today, 21:24
- Joined
- Dec 31, 2020
- Messages
- 1,026
Some of my systems had two or three BE databases linked to the FE all the time without any problems at all. Access doesn't care which tables it links, or if they are in different databases.
One for instance was a BE for skip hire and a BE for quarry and weighbridge operations. Each of these would have a separate program FE. If someone bought both programs then the programs would share data because the quarry system issued invoices separately to skips. The Quarry system would read the weighbridge via an RS232 serial cable and calculate the weight of product (sand and stone) removed from the quarry. It would also calculate the weight of waste incoming from the skips, with a weighticket related to each skip load. The waste weight was then charged on a skip invoice. Everything worked fine and without any issues with over 50 users in some cases.
One for instance was a BE for skip hire and a BE for quarry and weighbridge operations. Each of these would have a separate program FE. If someone bought both programs then the programs would share data because the quarry system issued invoices separately to skips. The Quarry system would read the weighbridge via an RS232 serial cable and calculate the weight of product (sand and stone) removed from the quarry. It would also calculate the weight of waste incoming from the skips, with a weighticket related to each skip load. The waste weight was then charged on a skip invoice. Everything worked fine and without any issues with over 50 users in some cases.
