Angus Murray Posted July 31, 2007 Posted July 31, 2007 I have a 'date received' field (defined correctly as a date field) that I use to identify whether a client has settled a bill or not. Using the '*' should show all records where this field has a date (ie the client has paid) and using '=' should find fields that are empty (i.e the client hasn't paid). Unfortunately the finds are not working. Any suggestions as to what could be going on? All other fields in the table and file (be they number or text fields) work fine with find commands. Many thanks in advance.
Genx Posted July 31, 2007 Posted July 31, 2007 what do you mean when you say the finds are "not working". They aren't returning anything, they're returning the incorrect sets?
Angus Murray Posted July 31, 2007 Author Posted July 31, 2007 Hi Genx - they are not returning any data at all. I have data in some of the ' date received' fields but the find (using '*') comes back with ' no records match this set of find requests'.
Lee Smith Posted July 31, 2007 Posted July 31, 2007 (edited) Are you performing the finds using Find Mode, or scripting it? If in Find Mode, the equal = sign, used by itself, will return any record that is BLANK in that field. The asterisk * should do the opposite, and find those records that have one or more characters. [color:blue] do not use the quotes in Find Mode it will find only those records with the asterisk in them in that field. What happens when you use the asterisk ? BTW, if you sort the records by the field you are performing the Find in now, the problems records are usually at the top, or bottom of the field. HTH Lee Edited July 31, 2007 by Guest
Angus Murray Posted July 31, 2007 Author Posted July 31, 2007 Hi Lee - thanks for your help and suggestions. I have figured out that I was using the "Date received" field as part of a calculation for another field on the same layout - I assume, although I'm only guessing, that you can't perform a find on a field that is being referenced by another field for a calculation. I have found a work-around anyway by creating a new field and using that for my find - thanks once again for your input.
comment Posted July 31, 2007 Posted July 31, 2007 I assume, although I'm only guessing, that you can't perform a find on a field that is being referenced by another field for a calculation. You most certainly CAN. There must be some other reason why your find is failing.
Recommended Posts
This topic is 6324 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