Thanks Andrew. Good stuff.
Good news Liz,
if you are going to start getting into SQL Server one day then you might want to work on the naming conventions early ;-)
Out of old habit, if my SQL Databases are going to be linked to anything like Access, I use "aaaaa" as prefix for the Primary Key index because older versions took the alphabetically first unique Key as the primary key. I'm not keen on prefixes otherwise, I'm more of a postfix type and Indexes tend to get called [Tablename_Fieldname_idx] which is usually unique.
As for caSe-senSitive, SQL Server can be either, depending on how it is installed and configured. T-SQL might not correct the capiTalisaTion of your coding as VBA does so you can end up with a piece of code working on a SQL Server with CI (Case Insensitve) sorting but not working when transfered to a production CS (Case Sensitive) Server.
Oh, be careful transferring code l! inking on Access DATE fields to SQL Server DATETIME Fields. Depending on how the fields are filled you can end up with values which won't JOIN because of value differences in the thousandths of a second on SQL Server.
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Posted by: Liz Ravenwood <Liz_Ravenwood@beaerospace.com>
|Reply via web post||•||Reply to sender||•||Reply to group||•||Start a New Topic||•||Messages in this topic (9)|