With not much to go on, I suggest that you examine each of the items
in the statement to see that they really are what you think they
are. Something may have been overwritten. In particular, start by
checking that oMyObject and oMyOtherObject are of type object, that
neither is .null., and that each refers to the correct class.
Well, I can't reproduce this error; it has only occurred once in the
lifetime of the application. Unfortunately my error handler doesn't
directly report the status of objects.
Upon looking closer, the last level in the call stack before the error is
triggered is the call:
oMyOtherObject.Method("fieldname")
The Error() method of that object comes next in the stack so presumably
that object exists.
Since VFP typically practices "lazy" parameter evaluation, I would also
assume that oMyObject.Method() encountered this error when it arrived at
that third parameter, which would imply that oMyObject also exists.
The table in question cannot contain NULLs; none of my tables can. However,
just to be sure, I also opened the table and did a LOCATE for
ISNULL(field). It didn't find any.
Thanks for any help.
Ken
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
