Unless you move the Data Environment Class to be the basis of your
business objects.
This could be fun, by the time we finish with all our favourite variants
we should have every common model worked out.
How about looking at some of the commercial frameworks or the 'Build
Your Own Framework with Visual FoxPro' book for ideas.
My version separates the data layer a couple of times as it is...
DataObject->DataBase.StoredProcedures->Data
The risk with this is that you can be temped to use part of the data
layer to deal with business logic problems which increases the
complexity of your system although it does make other sections clearer
[I have my own version of SQLExec that can take an array as the sql
script and catenate it together before calling the function but it is
much easier to write usp_GetAllActiveCustomers(liDays)] and can be a
huge win in terms of performance. This is one of those things like
normalisation where reality leaves the ideal behind a little.
--
Michael Hawksworth
Visual Fox Solutions
[EMAIL PROTECTED]
www.foxpro.co.uk
_______________________________________________
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.
