HELP! This originally seemed like a basic request until I started looking

into it.

SITUATION:

FM Solution A: Multiple database education solution served out on

FM5 Server on a LAN via TCP/IP. (OS9 - Mac server with both Mac and PC

clients) FM Solution A is mine.

FM Solution B: Multiple database library

solution served out on same FM5 Server as Solution A w/same connectivity. FM

Solution B is NOT mine and have little to nil knowledge of it.

The basic request is: Solution B wants "Name" and one or two other fields

from Solution A in a "LIVE" fashion. Example: Student 1 registers with the

school, and their info is entered in Solution A. Student 1 leaves the office

and walks over to the library to pick up their books for classes. Solution B

requires some of Student 1's info that was just entered in Solution A to now be in

Solution B.

Considerations:

- Cross Platform ability (ie: no AppleScript)

- Large Scale (For us): 40 clients on Solution A alone, a few less for Solution B

- Not necessarily the same list of students should be in each solution. (ie:

Solution A students may become "inactive" and deleted yet still have books

signed out in Solution B.)

- NO EXPORTING/IMPORTING FILES. Given how busy this situation

will be with the number of records and how often it has to be updated, this

doesn't appear to be an option.

- Security (Major Issue) Simple relationship connectivity is undesirable

as all other fields contained within the Solution A related db will become

available to Solution B. Some data in Solution A may be sensitive and

shouldn't be shared. Solution A is multi-level password protected.

Solution B, not sure yet. As well, one of the two FM solutions would

have to let the other know the full access level

password in order to set the relationships.

The Question Is: Given the situation, what method should be pursued?

ie: relationships, intermediate database.

Or am I going to have to give up one or more of my considerations?

ie: security, cross platform, etc.

I'm not looking for an exact answer on how to do it, rather suggestions based

on past experiences and results. (Unless of course you do know exactly how

to get it done.)

If I read your documentation right solution B should be view as a historical file (ie. live link won't work because of possible status changes).

So, here's how I would proceed. One - Solution A create Student ID|Active and Name|Active fields based on status Calcs (Status = Active) ID or Name. Inactive blank.

Solution B create a student ID Field. Assign to this field a value list looking into the Solution A file for Active Students. Relate the files via Student ID, and do look up for the other Solution A fields need in Solution B base on the ID relationship.

HTH

"- Security (Major Issue): Simple relationship connectivity is undesirable

as all other fields contained within the Solution A related db will become

available to Solution B."

Not so. This can be controlled by access passwords/groups/layouts. In sol'n A, create a layout called shared with only the fields you want to share. Create a share access level password (browse only) and group. Allow access only to that layout. Sol'n B can create a relationship that will access sol'n A data in the limited capacity.