Hi Frank,

I have been looking at using the methodology and
responses such as yours make my decision-making
process much easier.

Which methodology are you using?  Meaning, I know he
has wrote two books...the first having several
gotcha's and the second, from what I have heard, was
much better.

The ability to state stack objects as many levels as
needed, using the SetSuperState... GetSuperState
methods, seems to be very nice.  Are you using this
one (contains the mcolStack collection)?

Mac

--- fxvega@v... wrote:
> I myself have been using Lhotka?s VB6 Bus. Objects
> book and incorporating 
> his techniques into my client projects over the last
> year or two.  Here 
> are a couple of my personal observations/opinions
> about his method:
> 1) I feel using his object-oriented approach (versus
> a strict data-
> centric) approach makes an application more
> maintainable especially as the 
> application object model grows in size and
> complexity (as in complex 
> relationships between business objects and extensive
> business rules that 
> must be enforced).
> 2) In my opinion his object-oriented approach offers
> more 
> flexibility/adaptability on whatever backend
> "database" you use.  And yes 
> (even though I read articles that say things like
> "the object-oriented 
> approach is passé" or that "object-oriented
> components don't scale well") 
> Lhotka's approach does still allow one to use an
> "object-oriented 
> approach" to develop "distributable components" that
> are "state-less 
> objects" in the data-centric layer which would allow
> you to scale your 
> application physically. 
> 3) Yes, I have found a few ?gotchas? (and misprints)
> along the way as 
> others did as well.  However, my experience would be
> that the fixes were 
> nothing major.  If anything, working through these
> ?gotchas? did more to 
> improve my understanding and experience with his
> methods and therefore 
> also made it easier for me to adapt his methods here
> and there to fit my 
> preferences (as in my client's preferences) for the
> way something needed 
> to work.  For example, I modified his method here
> and there so that 
> OK/Apply will attempt to ApplyEdit all children of a
> parent object even if 
> an earlier attempt to apply edits to a child failed
> (somewhat of a batch 
> approach as in save/delete the children you can and
> then let the user 
> fix/cancel the children that did not save/delete).
> 
> I would also like to know if anyone in the
> metro-Denver area is 
> using/learning Lhotka?s approach and lives in the
> metro-Denver area.  I 
> would certainly be interested in talking more with
> you especially as I 
> move forward with his approach using his VB6
> Distributed Objects book and 
> into VB.Net.
> 
> Frank Vega
> Systems Analyst/Programmer
> VISS, Inc.