Getting there / Multi project DB

[esegal]

Okay, I posted before regarding getting one DB to handle multiple projects. I've added a ProjectsDB with solely project information (name, location, number, etc.), leaving a ContactsDB and a UserDB. The UserDB is where all the work is done. It's related to the ContactsDB for contact look-ups and the ProjectsDB for project information.

What I am trying to accomplish is that when a user opens the UserDB, they have to select what project they intend to work on, then not only will all other project records be omitted, but the ProjectDB info will auto-populate all new records until the project is changed.

I have a value list in the UserDB coming from (linked from) the ProjectsDB so they can select their project which then populates the "Project Name", "Project Location" and "Project Number" (among other) fields, but this is with all other projects records being present. What is the simplest way to isolate a projects records when selecting that project from a value list from another DB? Second, is there a pop-up value list that can run a find script when the item is selected?

I will keep browsing these vast archives, but any help or further questions would be appreciated.

[dbruggmann]

I'm not sure, what your User DB looks like:

Is there a record for every user? (Version A)

Or are there multiple records of diverse kind for every user? (version :

And I don't understand quite, why "the projects beeing present" bothers you. If you copy the ID number of the chosen project into a regular field (version A) or in global field (version : in thee UserDB, you should be able to reference all further work to this project (using scripts, calculations and/or look ups).

Anyway, the easiest way to isolate a record in the ProjectsDB (and omit all the others) would be a GTRR script step based on a relattionship between the projects ID in UserDB and the ID field in ProjectsDB:

[esegal]

Thanks, Dbruggman. I'll try to clarify: I currently have one database per project, but want to have one central DB into which I enter info pertaining to all projects. Each record has the projects info ("name", "number", "location") from the ProjectsDB AND the current users info ("entered by", "from", etc.) auto-entered from the ContactsDB into several fields (i.e. a transmittal for Project X by/from User Y). The problem I have with with Globals is a global field will change in past records which will confuse my co-workers to no end.

As for records for other projects being present: my colleagues are NOT computer savvy and I'm building this to cater to them. My idea is to have them select a project to work on and have every record present be only for that project. In other words, the UserDB "becomes" the projects DB. Otherwise they will flip through other projects records and get lost, confused and frustrated (believe me, I'm not exaggerating!). I'm looking for a simple, fool proof solution that they can't screw up.

I'll look into your recommendations today.