[AccessD]

Now I'm thoroughly confused as to whose head is being bashed and why.
You can create private Let and Get properties, although a private Get
seems pointless to me, since it will only be available within the class
module and you don't really need it there except maybe for symmetry.  A
private Let property, on the other hand, could be called and used within
the class itself, so it might be useful.  Now, which one of you was
wrong ... And about what???

Charlotte Foust

-----Original Message-----
From: Bryan Carbonnell [mailto:carbonnb at sympatico.ca] 
Sent: Friday, May 16, 2003 11:44 AM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD]


On 17 May 2003 at 1:05, Bruce Bruen wrote:

> However, re Bryan's comment - why can't the attribute value setting 
> code be private - fundamentally it's an attribute that <u>cannot</u> 
> be updated via this interface, but it does need to be visible to users

> of the class.  In this case the clubname is retrieved internally in 
> the class - it is a header for the object.
> 
> I don't believe that the public get/private let construct is 
> syntactically incorrect.  However, is it philosophically incorrect?  I

It's not. I made a boo-boo.

All VB(A) programming has taken a back seat for me these days. PHP is 
what I've been doing recently, so chalk it up to brain freeze.

Doh! (Bashes head against keyboard repeatedly) Doh! Doh! :)

Sorry 'bout that.

--
Bryan Carbonnell - carbonnb at sympatico.ca
Every time I close the door on reality it comes in through the 
windows.


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com