The reason is that database server is a Slackware, and I would rather that it is dedicated as a database server, and don't have to play file server now & then as we do have another server for that role. The idea was that I'd have the link point to a networked folder on the file server, and that "BE" would be just a copy of FE but with a local table instead of linked table to which each production copy of FE would examine. Therefore when I want to modify FE, I just swap in the Master FE with local table altered.
So that master FE would have a local table *and* a linked table pointing to it using the address of networked address; so it's self-referencing in that case. The production copy would be able a copy of the same FE but I'm assuming that the linked table inside would still point to the same networked folder (so is no longer self-referencing). The idea being that the master FE would be essentially the BE to check for new version. But to work, the production FE must have a linked table to the master FE's version table and since production FE is copied from the same master FE, the linked table has to be present in the master FE.... unless Bob''s utility automagically creates the linked table, (I'm suspecting not, based on Bob's recent post and his document)
I wouldn't know if I can even link a table in a database to its own table (will have to test when I'm in front of right computer) but wanted to make sure I wasn't overlooking any other issues with using Master FE as the version-checking BE.
So that master FE would have a local table *and* a linked table pointing to it using the address of networked address; so it's self-referencing in that case. The production copy would be able a copy of the same FE but I'm assuming that the linked table inside would still point to the same networked folder (so is no longer self-referencing). The idea being that the master FE would be essentially the BE to check for new version. But to work, the production FE must have a linked table to the master FE's version table and since production FE is copied from the same master FE, the linked table has to be present in the master FE.... unless Bob''s utility automagically creates the linked table, (I'm suspecting not, based on Bob's recent post and his document)
I wouldn't know if I can even link a table in a database to its own table (will have to test when I'm in front of right computer) but wanted to make sure I wasn't overlooking any other issues with using Master FE as the version-checking BE.