Re: Question to Interfaces/Objectcatalogue
- From: "Peter" <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Jul 2005 12:27:10 -0700
Hi Ralph.
Thank's for your answer. I see now, that an additional interface can't be
the solution. It doesn't pay anything. The mechanism of Interfaces and
Inheritance is quite plain to me. But I don't understand the basics of COM (I
think at this point, it's neccesary to read something about that ;-).
Unfortunately I have no bearing on this design of the project. Althoug the
concept of generated classes is not the worst thing. In a scenario with
hundreds of tables, it's not a good idea, to read from ADO Recordsets untyped.
And Code like rs.Fields("OrderNumber") can't be checked by the compiler.
That's a potential source of error.
Of course, the generated classes can't never be part of the bussines-layer.
That's absolutely clear. And that's not the circumstance in our project
(fortunately !)
There are a lot of additional classes and class-hierarchies, which are
designed for the bussines-layer. And together with the forms, we have now
this bloated Project.
Unfortunately, it's designed as a monolith.
We plan to remake the whole project in VB.NET or C#. But that's an
enterprise for the next few years.
Thank you,
Peter
.
- Follow-Ups:
- Re: Question to Interfaces/Objectcatalogue
- From: Ralph
- Re: Question to Interfaces/Objectcatalogue
- References:
- Question to Interfaces/Objectcatalogue
- From: Peter
- Re: Question to Interfaces/Objectcatalogue
- From: Ralph
- Question to Interfaces/Objectcatalogue
- Prev by Date: Re: Question to Interfaces/Objectcatalogue
- Next by Date: Re: Question to Interfaces/Objectcatalogue
- Previous by thread: Re: Question to Interfaces/Objectcatalogue
- Next by thread: Re: Question to Interfaces/Objectcatalogue
- Index(es):
Relevant Pages
|
Loading