Hi Matt.

>I would argue that to use no naming convention, you would have to be sure not to use reserved words [both in VFP and the back-end]. Your choice of field/table names would also have to be governed by reserved words in future versions of the backend.

First, you can get around the problem of using reserved words by putting quotes around them; for example, SELECT "PERCENT" FROM SOMETABLE. Second, avoiding reserved words makes good sense, but doesn't necessarily mean you have to use the Hungarian notation we typically use for variable and property names.

I'm not against having a naming convention for tables or fields; for example, I like the convention that many accounting systems have of prefixing table names with an abbreviation for the module, such as ARCUST for Accounts Receivable customers. One thing in my personal naming convention is that "ID" is the name of the primary key field in a table. However, naming a field cCompany to indicate that it contains character values just seems like a needless convention to me.

Doug