GlobalBank SQL Errors

Topics: CAB & Smart Client Software Factory
May 17, 2006 at 12:52 AM
originally posted by: fballem

There are still errors in the GlobalBank.sql script. I think it can be fixed through a global search and replace. The cause is due to the case sensitivity in SQL Express. If I understand it correctly, case-sensitivity is off by default, but some of us have turned it on when we installed SQL Express.

To fix the error: Find "CustomerID", replace with "CustomerId", make sure that the search is case sensitive.

Also, as some of us mentioned previously, the naming convention 'sp_' for the stored procedures does not conform to Microsoft recommended practices for naming stored procedures. I know that it will take some work to correct this (since they are referenced in code), but if this is being provided as a set of reference applications, then it should be right prior to release.

Hope this helps,