I guess I am not explaining this correctly (or not understanding correctly )
The relationship between the databases is one to one created on a uniqueID field within each database. I want to search through subset of records with UniqueIDs which are contained in both databases.
I thought that using a field that is linked by a relationship would allow me to only search the records in common between the databases. Is this not the case?
Let me spell out the situation in more detail than my last post....
I have 2 data bases:
A which has 25k records each with a UniqueID.
B which has 8K records each with a UniqueID
7K of the uniqueIDs are the same in each database. this is the set of records I want to search through. I want to be able to do many different finds, specifying different conditions, so I would rather not have to create a new relationship each time I want to pull out a different set of records.
So I created a layout in A and put a calculated field from B (B:calcfield) into it. The relationship used is A:uniqueID to B:uniqueID
Now if I go into database B directly and do a find in calcfield (>2) I get 240 records which all have a value >2 for calcfield. So far so good.
If I then go into database A and go to the B:calcfield and do the same find (>2). I get 220 records, 200 of which have a value >2 for B:calcfield BUT 20 of which have a value <2 for B:calcfield.
So it is returning records that don't match the criteria that I have specified. And this is my problem. I have checked that the relationship is indeed one-to-one. The spurious records don't share a uniqueID with the records that are getting pulled out. It isn't searching the current database, becasue the field that I have selected doesn't exist in the current (A) database
Does this explain my problem better?
thanks
Ivan