BCM 2007 typo alert

BCM 2007 typo alert

If you are using the September 2006 version of this document to install your Outlook 2007 with Business Contact Manager database on a server, you need to watch out for a couple of critical typos in the sqlcmd statement on page 9.

First, you need to understand that the way the document is formatted, it looks like there are a series of commands here, several of which start on a new line. That is not right. The command needs to be given all at once, with nothing but spaces where it looks like you need carriage returns.

Second, you will notice that the command ends with a double-quote (“), but there is no double-quote earlier in the command so the statement is invalid. There should be a double-quote before the word CREATE right at the beginning of the command.

So here’s what the command actually looks like for me, run from a command prompt on my Small Business Server:

C:\>sqlcmd -S .\MSSMLBIZ -E -Q “CREATE DATABASE [BCM_DB] ON (NAME = N’BCM_DB_dat’, FILENAME = N’F:\BCM2007\BCM_DB.mdf’, SIZE = 25, FILEGROWTH = 50%) LOG ON (NAME = N’BCM_DB_log’, FILENAME = N’F:\BCM2007\BCM_DB.ldf’, SIZE = 10,FILEGROWTH = 50%) Collate SQL_Latin1_General_CP1_CI_AS exec sp_dboption N’BCM_DB’, N’autoclose’, N’false’ exec sp_dboption N’BCM_DB’, N’bulkcopy’, N’true’ exec sp_dboption N’BCM_DB’, N’trunc. log’, N’true’ exec sp_dboption N’BCM_DB’, N’torn page detection’, N’true’ exec sp_dboption N’BCM_DB’, N’read only’, N’false’ exec sp_dboption N’BCM_DB’, N’dbo use’, N’false’ exec sp_dboption N’BCM_DB’, N’single’, N’false’ exec sp_dboption N’BCM_DB’, N’autoshrink’, N’false’ exec sp_dboption N’BCM_DB’, N’ANSI null default’, N’false’ exec sp_dboption N’BCM_DB’, N’recursive triggers’, N’false’ exec sp_dboption N’BCM_DB’, N’ANSI nulls’, N’false’ exec sp_dboption N’BCM_DB’, N’concat null yields null’, N’false’ exec sp_dboption N’BCM_DB’, N’cursor close on commit’, N’false’ exec sp_dboption N’BCM_DB’, N’default to local cursor’, N’false’ exec sp_dboption N’BCM_DB’, N’quoted identifier’, N’false’ exec sp_dboption N’BCM_DB’, N’ANSI warnings’, N’false’ exec sp_dboption N’BCM_DB’, N’auto create statistics’, N’true’ exec sp_dboption N’BCM_DB’, N’auto update statistics’, N’true'”

To modify this command for your own use, you’ll need to change the variables MSSMLBIZ, BCM_DB, and F:\BCM2007 to fit your particular environment. This will make more sense once you read pages 9 and 10 of the instructions.

Thanks to Mehul Shah at Microsoft for working with me to find the typo in the document and giving me the correct information.

There may be additional roadblocks later in the document. If I come across any, I’ll let you know.

Posted in All, BCM, Office 2007, Software, Technology on Dec 18th, 2006, 8:31 pm by David Schrag   

2 Responses

  1. January 20th, 2007 | 7:24 pm

    […] Outlook 2007 finally talking to shared BCM database on SBS 2003 I wrote earlier about problems I was having configuring Outlook 2007 with Business Contact Manager to use a database on my server rather than on my own workstation. Even after dealing with the typo in the instructions, I couldn’t get Outlook to detect the presence of my database on the server. I was really confused, because I had no trouble connecting to the database using Access. So I knew the database was there on the server, ready and able to communicate. […]

  2. February 10th, 2007 | 6:59 pm

    […] How hard is it to fix a typo? Microsoft came out with instructions for installing Outlook 2007 with Business Contact Manager on a server last September. It’s a great document, but (a) it was written for the Beta version of Outlook 2007 and hasn’t been updated to show that it also applies to the RTM version, and (b) more importantly, it has a typo, as I’ve already pointed out. […]

Leave a reply