Hi Dustin.

>I'm reading through "SQL Server 7.0" WROX book (highly recommended by many) and I noticed that their naming convention for field names do not use "c" or "i" or "n" (or anything else) before the field names to denote TYPE. (Example = nCustomerNumber, cName, tOrderDate)
>
>Usually in XBase examples, you see everyone doing this.
>However, in SQL I see this less. Anyone have any thoughts on this? What are your normal procedures? Is it a 'waste' of time to do this in SQL or something?

Actually, I think this is a waste of time in xBase too. It makes sense with variables because xBase is weakly typed (meaning you can put any value into any variable), so a naming convention tells the developer what data type is expected in a variable. However, fields in tables are strongly typed, so there's no need to use a naming convention to tell you the expected data type; just look at the table structure.

My 2 cents (and I'm guessing I'll hear some opposing opinions <g>).

Doug