In the creatobject line it returns 'class definition frmCoach is not defined'.
It must be me...
Well, that was just an example.
In order to communicate with an object in VFP, one must have an object
reference to it. I was using the class method.
You can also do
DO FORM frmCoach NAME oFrmCoach
This will create oFrmCoach as an object reference to the form.
(Please see the VFP Help on DO FORM and look at the "LINKED" keyword;
otherwise you can end up with "dangling" object references.)
Another way to do this is with macro substitution:
DO FORM frmCoach
&frmCoach..Top = 5
"frmCoach" is just a name; it is not an object reference. Using the "&"
prefix causes VFP to evaluate the name and resolve it to an object
reference. But this will only work where "frmCoach" is in scope--that is,
in the same method, function, or procedure where you issued DO FORM.
WEXISTS() doesn't work off object references; it's a whole other pre-OO
xBase thing.
Ken Dibble
www.stic-cil.org
_______________________________________________
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.
