Bryan VonDeylen Posted February 14, 2013 Share Posted February 14, 2013 I have a FP12 database where I am using our SIS database (Infinite Campus) tables. In FileMaker relationship, I want to find classroom rosters. The relationship I have setup between FileMaker and a roster table from IC is: Globals <-> dbo.Roster SectionID = sectionID and Null = endDate In Infinite Campus (IC), when a student drops a course, the endDate field has the date they dropped, otherwise the field is empty (null). BUT, it appears that FileMaker will NOT match a "null" field. If the field in IC does not contain anything, it will not match a field in FileMaker that does not contain anything (is null). Is this a bug, or just the way it is??? Link to comment Share on other sites More sharing options...
Lee Smith Posted February 14, 2013 Share Posted February 14, 2013 Have you tried the isValid Function? Link to comment Share on other sites More sharing options...
Rick Whitelaw Posted February 15, 2013 Share Posted February 15, 2013 Not a bug. To be used as a match field it only makes sense that both fields contain data. Link to comment Share on other sites More sharing options...
Wim Decorte Posted February 15, 2013 Share Posted February 15, 2013 Not a bug. To be used as a match field it only makes sense that both fields contain data. At the very least the field on the side/context where the relationship is being evaluated from. The matched field can be empty and the relationship would still be valid. Link to comment Share on other sites More sharing options...
Bryan VonDeylen Posted February 23, 2013 Author Share Posted February 23, 2013 Lee, not sure what you mean. I cannot use a Function in a Relationship graph. Rick, if it isn't a bug, than I guess it would be a feature request for a future version. Wim, it doesn't. The relationship is not valid if nothing is in the sql table field (thus the thinking it was a bug). I am guessing it needs to be a feature in a future update. I took care of the issue by designing a search instead of relying on a relationship. Link to comment Share on other sites More sharing options...
LaRetta Posted February 24, 2013 Share Posted February 24, 2013 Oh don't give up on this technique! You can relate to empty child records if the data type is number or date because you can use a > from single unstored calculation string of 0 or from calculation Date ( 1 ; 1 ; 1 ) to the child (same data-type) field (please see attached). I wasn't quite clear on your relationships but I hope this gives you an idea - it is very siimple. NullRelation.zip Link to comment Share on other sites More sharing options...
David Jondreau Posted February 25, 2013 Share Posted February 25, 2013 Make a calc field on the child side = IsEmpty ( endDate ) and make a calc field on the parent side = 1 and match on those two fields instead of Null = endDate. Globals <-> dbo.Roster SectionID = sectionID and Null = endDate Link to comment Share on other sites More sharing options...
LaRetta Posted February 25, 2013 Share Posted February 25, 2013 Hi David, Why add two new calcs when you only need one? :-) Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 4086 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now