Re: decouple gui from bo
- From: "MP" <NoSpam@xxxxxxxxxx>
- Date: Mon, 23 Jul 2007 10:57:42 -0500
"MP" <NoSpam@xxxxxxxxxx> wrote in message
news:%23ny462TzHHA.4004@xxxxxxxxxxxxxxxxxxxxxxx
principle was recommended to decouple gui from other classes
What you abandoned was the better solution.
just to recap
My orig design:
Dim f As frmX
Set f = New frmX
Set f.Clients = New cClients
'that line created the cClients collection class which compiled a list of
clients which frm used to load the list box with their names
are you saying that's permissible to let frm know about cClients and cClient
class in order to achieve the simplicity of that call?
I just thought someone had said that a form should not know about the other
classes in the project???
.
- Follow-Ups:
- Re: decouple gui from bo
- From: Ralph
- Re: decouple gui from bo
- References:
- decouple gui from bo
- From: MP
- Re: decouple gui from bo
- From: Ralph
- Re: decouple gui from bo
- From: Ralph
- Re: decouple gui from bo
- From: MP
- decouple gui from bo
- Prev by Date: Re: Parent object question
- Next by Date: How do I set up SQL Server Express to be shared on network (using VB 6.0)
- Previous by thread: Re: decouple gui from bo
- Next by thread: Re: decouple gui from bo
- Index(es):
Loading