Tracy,

I'll give you mine.

>We are compiling system limitations and coding standards for our company. We code in VFP, Delphi, VB.NET, and WebSmart among others. We are compiling an 'accepted' practice of coding standards for EACH language (since there are typically habits developers in each language employ that are not necessarily accepted universally). This is everything including (but not limited to):
>
>indentation of nested blocks

Indentation is a minimum of two spaces. Since indentation is meant to display logical or iterative sub-ordination, this means that with a SELECT CASE statement, each CASE/OTHERWISE is indented and the code sub-ordinate to these clauses is also indented.

>comments

Simple and straight forward. Comments should tell the why, not the how, of well written, self-documenting code. Fancy formatting strictly prohibited. The reason for this is that the formatting itself poses a problem in keeping modifications commented properly. IOW, it's a PITA with fancy formatting to keep comments up to date.

>identifiers (common abbreviated standard or spelled out)

No abbreviations allowed.

>variable naming conventions

Standard Hungarian

>objection creation/destruction standards

In general, and unless there's an overriding reason not to do so. Objects are created and destroyed within the scope of the individual modules.

>font face on forms

None really, but I tend to use Tahoma since it's the Windows standard.