[AccessD] New poll on TechRepublic.com

Shamil, I don't purposely leave out options in polls, but the truth is, it 
makes no difference how carefully I word the items or how much thought goes 
into a set of responses, someone still wants an item I didn't offer. :) It 
happens with every single poll. That's why we keep the responses on for 
polls, so people can include thoughts beyond what the polls present.

I find adding a prefix tag to a table, query, form, or report redundant and 
unnecessary -- other than it does allow you to have like named tables and 
queries. The truth is, that's never been an issue for me as queries tend to 
have more meaningful names than just copying a table's name. When using code 
to create an object, I can see why you'd want to clearly identify the object 
by adding a prefix tag.

I have found the .NET conventions a little hard to follow when reading code, 
but that's because I don't really use it.

Feel free to add your thoughts to the forum discussion.

Susan H.


> Hi Susan --
>
> I'd note that in your poll:
>
> How do you name Access objects?
>
>    * I use a prefix for everything, even Access objects.
>    * I use the natural naming method for Access objects.
>    * I'm stuck with a convoluted business-ruled naming convention, so it
> doesn't matter what I prefer.
>    * I don't use a naming convention.
>    * I use some other naming convention.
>
> at least one entry is missing, which is worth to be clealy defined
> additionally to "I use some other naming convention":
>
>   * I use a prefix for everything, even Access objects except MS Access
> tables', fields' and indexes' names.
>
> Using prefixes for Access objects was useful (for grouping and sorting in 
> db
> window) when there was no a feature of grouping MS Acces objects in MS
> Access database container.
> Another purpose (at least for me) was (automated) documentation in which
> consistent three-four letters long lowcase prefixes were useful
>
> It's redundant to use such prefixed now IMO - I'd use suffixes (as it's
> recommended in .NET Naming Guidelines) or nothing.
> Still using "Hungarian Notation" for VBA coding is useful as it lets to
> clearly see what this or that name means.
> Although being more .NET developer than MS Access/VBA one these days I'm
> starting to avoid using Hungarian Notation even in VBA code - and it looks
> as a natural approach to me.
>
> Thank you.
>
> --
> Shamil
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
> Sent: 15 ??????? 2010 ?. 2:16
> To: Access Developers discussion and problem solving
> Subject: [AccessD] New poll on TechRepublic.com
>
> <http://blogs.techrepublic.com.com/msoffice/?p=3957&tag=leftCol;post-3957>
>
> Feel free to take part. You don't have to have a subscription to vote or
> take part in the response threads.
>
> Susan H.
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com