D
dr.jian.qin
Hi all,
I have successfully found a walk-around solution to share BCM offline:
Server side:
1. Install a full version of SQL 2000 on a server (Windows 2000 or
2003), then install Outlook 2003 and BCM v2 with all service packs.
2. Un-install the MSDE instance MicrosoftSMLBiz.
3. Go to registy of the server to switch BCM to use the default server
and default TCP port 1433.
4. Create a BCM database (like MSBCM) in Outlook.
5. Go to Enterprise Manager to make the default SQL 2000 a publisher
and make MSBCM database as a publication (allow anonymous subscription,
and replicate everything).
7. Add Your Domain\Domain Users into Public Access List of this
publication.
7. Publish this publication in Active Directory
Client side:
1. On Win XP, Install Outlook 2003 and BCM v2 with all service packs.
2. In Outlook, create a database locally called MSBCM (the same name as
the database on the server).
3. Go to Start/Programs/Accessories/Synchrozine
4. You will see an option to create a subscription. Follow the
instruction to create a subscription by looking for publication in
Active Directory and using the local MSBCM database as subscriber's
database.
5. Set up the sycn schedule inside of Synchronize Manager (on idle, log
on/off, etc)
6. Repeat the steps above to set up other clients.
Now changes made either from server or client(s) will be able to sync
together. Client can take the laptop offline and later sync the
changes after re-connect to the LAN network.
Special Note: a while ago, some one was able to set up the replication
but the client Outlook crashes every 15 minutes -- I had the same
problem initially. After troubleshooting, I found out the reason: if
you use "create a subscription" process to create a new database on
your client side, the database will miss a role called
"db_SharedUsers", and then Outlook crashes. My walk-around will be to
create a BCM database before you set up the subscription. Of course if
you have Enterprise Manager installed on the client side, you can
always add that role. Or other SQL command tools can do the same.
Problem so far:
Most of parts work fine. But I have one unconfirmed concern: since
the replication is not the really "sharing the database" -- BCM may
have problem with recording each user's activity. In another words, it
may treat all changes from different clients as one user. This is just
my guess and I will confirm this later on.
Good luck!
I have successfully found a walk-around solution to share BCM offline:
Server side:
1. Install a full version of SQL 2000 on a server (Windows 2000 or
2003), then install Outlook 2003 and BCM v2 with all service packs.
2. Un-install the MSDE instance MicrosoftSMLBiz.
3. Go to registy of the server to switch BCM to use the default server
and default TCP port 1433.
4. Create a BCM database (like MSBCM) in Outlook.
5. Go to Enterprise Manager to make the default SQL 2000 a publisher
and make MSBCM database as a publication (allow anonymous subscription,
and replicate everything).
7. Add Your Domain\Domain Users into Public Access List of this
publication.
7. Publish this publication in Active Directory
Client side:
1. On Win XP, Install Outlook 2003 and BCM v2 with all service packs.
2. In Outlook, create a database locally called MSBCM (the same name as
the database on the server).
3. Go to Start/Programs/Accessories/Synchrozine
4. You will see an option to create a subscription. Follow the
instruction to create a subscription by looking for publication in
Active Directory and using the local MSBCM database as subscriber's
database.
5. Set up the sycn schedule inside of Synchronize Manager (on idle, log
on/off, etc)
6. Repeat the steps above to set up other clients.
Now changes made either from server or client(s) will be able to sync
together. Client can take the laptop offline and later sync the
changes after re-connect to the LAN network.
Special Note: a while ago, some one was able to set up the replication
but the client Outlook crashes every 15 minutes -- I had the same
problem initially. After troubleshooting, I found out the reason: if
you use "create a subscription" process to create a new database on
your client side, the database will miss a role called
"db_SharedUsers", and then Outlook crashes. My walk-around will be to
create a BCM database before you set up the subscription. Of course if
you have Enterprise Manager installed on the client side, you can
always add that role. Or other SQL command tools can do the same.
Problem so far:
Most of parts work fine. But I have one unconfirmed concern: since
the replication is not the really "sharing the database" -- BCM may
have problem with recording each user's activity. In another words, it
may treat all changes from different clients as one user. This is just
my guess and I will confirm this later on.
Good luck!
