Hi Nicolaas,
The thread is incomplete so I may be missing the point of your post. Also,
the first part I see is a response to an email???
If all you want to do is store values then a table will do it better than
anything else. I seem to recall a thread originated by you in the last few
days about classes so I assume this discussion is still about that.
First, a confession: I've been so busy doing other things and nothing at
all that I haven't really gotten into classes and objects. But I do know
that they are great! A class module is a "cookie cutter" you design it to
have all of the properties and behaviors that you want the objects of that
class to have. You can then create any number of instances of objects (the
cookies). If you want to change something about the class, you change it in
the class module and thereafter all of the objects you create from that
class will have the new behavior or properties.
Ken Getz has included a chapter or so in the last several editions of The
Access [YourVersion] Developer's Handbook from Sybex. Deborah Kurata has
written a few books about Doing Objects in Microsoft Visual Basic
[YourVersion].
Storage is more of an issue than you might have imagined. Variable
information that must persist across sessions must be stored in a file or
table.
To directly address your question about Let and Get: You can validate the
argument passed in with the let and be sure it fits your paradigm. You can
also have the Let initiate some other process inside your object which would
be beyond the capabilities of an Access table. The same is true of the Get.
Also, you are not making the actual variables visible to the using program,
only the properties via your code.
There are snippets of information available all over the internet but I
recommend going for a good book first.
HTH
--
-Larry-
--
"WindAndWaves" <ac****@ngaru.com> wrote in message
news:Cw********************@news.xtra.co.nz...
another dumb question, further to this let and get discussion.
Would it not be much easier to store values in a (temporary) table???
this just seems a lot more tangible.
"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40******@news.microsoft.com... Yes, they were -- and are a useful way to wrap global variables. But
their primary purpose is for use in classes.
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
This posting is provided "AS IS" with
no warranties, and confers no rights.
"Lyle Fairfield" <ly***********@netscape.net> wrote in message
news:2h************@uni-berlin.de... Douglas J. Steele wrote:
> This is done in conjunction with classes.
But let and get properties were enabled for standard modules in AC2K.
---
Please immediately let us know (by phone or return email) if (a) this
email contains a virus
(b) you are not the intended recipient
(c) you consider this email to be spam.
We have done our utmost to make sure that
none of the above are applicable. THANK YOU
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.690 / Virus Database: 451 - Release Date: 22/05/2004