The question frequently arises, after a Pathagoras network is established:
"Ok, now what do I do with my Instant Database files?"
And the answer is, "Anything you want."
•You can leave all IDB records where they are.
•You can move all IDB records to a common location.
•You can share your local records, or not.
•You can share the matter records and not the masks, and vice versa.
•You can maintain one set of matter records or masks, or both, on your local drive and another set on the network. That way, you can keep some records and masks 'personal' and others you can share on the network.
Pathagoras imposes no requirements, just alternatives. (We know that Pathagoras' steadfast refusal to impose 'this is the way it has to be done' requirements is unsatisfactory to many. But hey, that's what makes us so popular.)
So, you have to decide what you want to do. Once you make that decision, Pathagoras makes it easy to implement. You can set and change Pathagoras file locations, and decide what you are going to keep local and what you are going to keep in a common location, from the Instant Database File Locations screen. Click the link to be taken to the page that discusses it.
The Network files tab under the Utilities/Settings screen allows you to upload and down load Masks and Matter records to and from the Common Profiles Path. Be mindful of the difference between uploading an InstantDatabase mask to the Common Profiles Path (or downloading one from the CPP) and ‘sharing a common Instant Database Mask’.
a.In the former situation, you are simply transferring the 'physical' record from one location to another. A file that was downloaded from the CPP will look like the original file that was uploaded, but it is not ‘the same file.’ You are not technically sharing the file, so much as you are working from a file that looks like the original. You can make changes to the original or copy of the Mask or Matter record, and it will not affect the other copy. (And this would explain why, when one user changes the mask and the other user who had a copy of the mask, does not see the change.)
b.In the ‘sharing' scenario, the IDB pointers on the individual computers all point to the same file on the network. The end users (and the administrator) should all set their IDB file pointer to a common location. This is done via the InstantDatabase Tools|File Locations page. A change to the mask or the matter record will be seen by all users who share the common mask.
c.You might prefer to transfer matters and masks to and from the CPP if (1) if most users on the network operate as stand alone operations, rarely sharing data; or (2) are frequently away from the network or (3) rarely have a need to use the masks created by another user. In these situations, the administrator should upload ‘community’ masks to the CPP. The end-users should be instructed to download one or more of the masks to their local drives. When changes are made to a mask, the revised masks are sent up to the CPP, overwriting the original copy, and end-users are advised of the change and instructed to download the newest version.