Re: Classes With a Form

Tech-Archive recommends: Speed Up your PC by fixing your registry

"J French" <erewhon@xxxxxxxxxx> wrote in message
news:4316e4dd.273046638@xxxxxxxxxxxxxxxxxxxxxxx
> He was worried that you would make your code obscure and confusing
> - he is quite correct, using UDTs irresponsibly could make a right
> dog's dinner out of a nice granular bit of code.

I remember reading in ms access newsgroup that one user named related fields
in different tables the same, for example, if they had customer and invoice
tables the tables might look something like this

--Customer table
CustomerID
FirstName
FamilyName
DOB
etc

--invoice table
InvoiceID
CustomerID
Amount
etc

The reason they said they did this was because of the autojoin feature when
writing queries automatically joined CustomerID and CustomerID. I remember
thinking that this is not a reason you should consider when naming fields.
Fields should be given a name based on what best describes the fields, not
on what features in the language will do with those fields.

I thought your example was similar in that you were choosing how to name
variables based on the intellisense feature. You don't really need the dot
anyway to use intellisense, I just type a few chrs and push ctrl space.

Michael


.