I've recently run into something that surprised me. The company that I recently starting working for has a VFP application that uses MS-SQL 2000 as the database. When I first tried using the Query Analyzer my queries kept coming back with errors saying the table or column did not exist. The same was true for queries I submitted via SPT from VFP. Finally I discovered that they have set up the database and MS-SQL Server as being case sensitive which means that when you reference an object the names have to match. I use 'camel notation' when I name my objects and the existing database uses all lowercase names, therefore no match... In my previous position our MS-SQL 2000 was set up to be case insensitive. Apparently this is a one time setting you can only do when you first set up MS-SQL, so it's too late to change that now.

Anyway, this being the case and if you don't mind sharing your expertise, what are the best coding practices for coding in such an environment? I don't like the idea that I have to code with some data names being lower case (those in a table) and others (memvars, etc.) being in mixed case. I find it hard to believe that MS would come out with something like this because to be best of my knowledge you wouldn't want to maintain two tables with the same names and the only difference would be the case they are named in. The same would be true for columns, SP's, indexes, etc.

Jim White