Good point, Colin.
The GetObject function MIGHT do it in certain rare cases, but I think the complexity of the rare cases pretty much prevents it from being useful. At least IN THEORY since you can provide a path to your app when using GetObject, you could provide a path including a node name. But you would need to know every potential node where it COULD run AND you would have to be running as a network admin (or more) to be able to look into another machine anyway. Technically, you could perhaps do it - but practically, in most managed domains, you would never have permission to do it.
Therefore, using something internal to the DB - like a single-record BE table - is probably going to be the only reliable way to get this effect. Which falls under one of my favorite bits of advice: Access won't tell you anything you didn't tell it first. Want Access to tell you if something is in use? Have tje Access function that uses that something tell Access it is in use. Which means "in a table in the BE" due to scope issues.