Atomic Shrimp
Humanoid lifeform
- Local time
- Today, 05:21
- Joined
- Jun 16, 2000
- Messages
- 1,954
I'm working on an application designed to be a companion to a third-party, standalone Access application that is not split.
So my app will have a lot of its own tables, and these will be in a back end on a server, and will be linked in all instances of the front end.
But it will also have links to tables in the third party application - these will only work on one machine only (the one on which the application is installed).
I don't want to develop and maintain two different versions of the front end - I want to enable the functions that touch the third party linked tables only on the machine where they will work.
What's the best/most reliable way to detect whether a linked table is in working condition?
So my app will have a lot of its own tables, and these will be in a back end on a server, and will be linked in all instances of the front end.
But it will also have links to tables in the third party application - these will only work on one machine only (the one on which the application is installed).
I don't want to develop and maintain two different versions of the front end - I want to enable the functions that touch the third party linked tables only on the machine where they will work.
What's the best/most reliable way to detect whether a linked table is in working condition?