Andy Davies wrote:
Yup, he was right and I was wrong - I had the rowsource as aMydata instead
of thisform.aMydata - and instantiating the busobj/dataobj in the form load
(as suggested by Michael Babcock) also works - although I'm working towards
something more elegant than' thisform.[oBiz.]oData.cMyText' that does work
just fine.
There's a couple different ways you could do it: you could bring back
an object to the UI layer and make it a part of a record object there
(so the controlsource is thisform.oRecord.cName, for example), or you
could create the record object in the Biz layer and have your UI map to
that (so the controlsource for this example would be
thisform.oBiz.oRecord.cName if you brought the object back to the Biz,
or thisform.oBiz.oData.oRecord.cName if you so choose to do it that
way). There are so many ways to do it with the Fox in many
things...this is another prime example. For me personally, I don't like
to couple things or make dependencies; that's why I basically pass the
record object among the tiers. Loose coupling facilitates easier
testing, imo, and offers more flexibility, recalling the best practice
of programming to the interface, not the implementation.
--Michael
--
Michael J. Babcock, MCP
MB Software Solutions, LLC
http://mbsoftwaresolutions.com
http://fabmate.com
"Work smarter, not harder, with MBSS custom software solutions!"
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** 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.
