Outlook BCM 2003 to BCM 2007 - Lost All Contacts

[Guest]

So when I isntalled the new BCM 2007, I did not backup my business contacts.
A major error on my part. I did do a .pst backup for my calendar, email, etc.

I recieved an error that the database migration was unsuccessful so I just
created a new database. I have tried to switch back to what I believe to be
my old BCM 2003 contacts, but I receive the same migration unsuccessful
error. Are my BCM 2003 contacts stored somewhere that I can retrieve them or
am I just out of luck? Can anyone take a look at my .sbb file to try and
recover it?

Please help!

Thanks,
coop

 

[Luther]

1) You should report the migration error to Microsoft so that they can
fix it before they release the product. That's the point of the beta.

Before migration, BCM backs up the database, the sbb file. I think
that's just a zip file containing a sql backup file.

2) If the bug gets fixed, then in the final release of BCM you should
be able migrate the backup up db to 2007.

3) You should be able to restore the database on a machine with BCM
2003, export the data to a BCM file, and then import that file in BCM
2007.

 

[Guest]

I am somewhat confused. How am I supposed to export the data to a bcm file
if I cannot access it. I could not import the database (.sbb file) into a
2003 machine because that file format is not recognized.

Anyone's help is much appreciated.

 

[Guest]

I had the same problem. I have used office 2003 outlook w BCM for a year for
my small business. When i downloaded the new version of BCM and installed it,
it couldnt read in the old file format, which was very frustrating. Some
error message telling that the format was not recognized were driving me
crazy. then I decided to go back to the previous version. As I was lucky i
had a backup so it worked.
The data files are saved in " .. documents and settings\your username\local
settings\microsoft\business contact manager\......" but the files had other
endings than .SBB.

Does any one has a go around?
Daniel

 

[mrtimpeterson via OfficeKB.com]

Reading this post brings a chill to this Autumn air! With BCM 2007 getting
so close to a final release date, it amazes me that such a major feature
related to migration of data from the 2003 version forward still has flaws.
Maybe someone did not think this was going to be important enough to
prioritize upon. Never mind that this problem could affect just about EVERY
current user now on BCM v.2. I realize that the very nature of beta
releases is to rely upon end user feedback to alert the designers on how to
tweak and refine the public release version. Instead of reactively relying
solely upon an end user to report this to Microsoft so it can be fixed, I
would assume that Microsoft would have a team of testers constantly migrating
different sets of data themselves with the "proactive" agenda of identifying
such a major problem internally.

For all end users who are currently using the current BCM v2 release in their
business, let this be a warning that BCM v3 (2007) is NOT a public release
yet. As eagerly awaited as it may be by so many tired of the old limited
features of the current version, it will likely be some time yet before the
next version is truly ready for real world adoption. Even after the public
release, it may be helpful to remember that there will likely be some
embarrasing discoveries related to major oversights of the beta process.
Microsoft is known for its unofficial continuance of "beta-like" releases to
the public.

Let the Buyer beware!

-THP

I had the same problem. I have used office 2003 outlook w BCM for a year for
my small business. When i downloaded the new version of BCM and installed it,
it couldnt read in the old file format, which was very frustrating. Some
error message telling that the format was not recognized were driving me
crazy. then I decided to go back to the previous version. As I was lucky i
had a backup so it worked.
The data files are saved in " .. documents and settings\your username\local
settings\microsoft\business contact manager\......" but the files had other
endings than .SBB.

Does any one has a go around?
Daniel

I am somewhat confused. How am I supposed to export the data to a bcm file
if I cannot access it. I could not import the database (.sbb file) into a

[quoted text clipped - 29 lines]

 

[Luther]

V2 to V3 migration has worked with every database and backup file I
tried it on.

Tim, do you have a file with which that's not the case?

Reading this post brings a chill to this Autumn air! With BCM 2007 getting
so close to a final release date, it amazes me that such a major feature
related to migration of data from the 2003 version forward still has flaws.
Maybe someone did not think this was going to be important enough to
prioritize upon. Never mind that this problem could affect just about EVERY
current user now on BCM v.2. I realize that the very nature of beta
releases is to rely upon end user feedback to alert the designers on how to
tweak and refine the public release version. Instead of reactively relying
solely upon an end user to report this to Microsoft so it can be fixed, I
would assume that Microsoft would have a team of testers constantly migrating
different sets of data themselves with the "proactive" agenda of identifying
such a major problem internally.

For all end users who are currently using the current BCM v2 release in their
business, let this be a warning that BCM v3 (2007) is NOT a public release
yet. As eagerly awaited as it may be by so many tired of the old limited
features of the current version, it will likely be some time yet before the
next version is truly ready for real world adoption. Even after the public
release, it may be helpful to remember that there will likely be some
embarrasing discoveries related to major oversights of the beta process.
Microsoft is known for its unofficial continuance of "beta-like" releases to
the public.

Let the Buyer beware!

-THP

I had the same problem. I have used office 2003 outlook w BCM for a year for
my small business. When i downloaded the new version of BCM and installed it,
it couldnt read in the old file format, which was very frustrating. Some
error message telling that the format was not recognized were driving me
crazy. then I decided to go back to the previous version. As I was lucky i
had a backup so it worked.
The data files are saved in " .. documents and settings\your username\local
settings\microsoft\business contact manager\......" but the files had other
endings than .SBB.

Does any one has a go around?
Daniel

I am somewhat confused. How am I supposed to export the data to a bcm file
if I cannot access it. I could not import the database (.sbb file) into a

[quoted text clipped - 29 lines]

Thanks,
coop

 

[mrtimpeterson via OfficeKB.com]

Luther,

I do not use BCM. Both Daniel & Coop have indicated in their posts above
that "they" have experienced migration difficulties however and this caught
my attention and motivated me to reply with my cautionary warning. BCM v. 3
is still a Beta release and to see problems from users trying to already rely
upon it for their real world business needs already is very surprising.

I will not even consider using BCM version 3 until well after the first
public version is released and then inevitably updated with numerous fixes.
This is the MS way because they dominate the software industry. Once V3 is
more established hopefully sometime in the future, I will take a look at
potential applicability for real world needs. Until then, like many, I just
can't waste the time being an experimental lab rat with such a vital tool for
my everyday business requirements.

BCM has great potential and perhaps one of these years it will eventually get
much closer to fulfillment of such potential.

-THP

V2 to V3 migration has worked with every database and backup file I
tried it on.

Tim, do you have a file with which that's not the case?

Reading this post brings a chill to this Autumn air! With BCM 2007 getting
so close to a final release date, it amazes me that such a major feature

[quoted text clipped - 45 lines]

Message posted via OfficeKB.com
http://www.officekb.com/Uwe/Forums.aspx/outlook-bcm/200610/1

 

[mrtimpeterson via OfficeKB.com]

Luther,

I do not use BCM. Both Daniel & Coop have indicated in their posts above
that "they" have experienced migration difficulties however and this caught
my attention and motivated me to reply with my cautionary warning. BCM v. 3
is still a Beta release and to see problems from users trying to already rely
upon it for their real world business needs already is very surprising.

I will not even consider using BCM version 3 until well after the first
public version is released and then inevitably updated with numerous fixes.
This is the MS way because they dominate the software industry. Once V3 is
more established hopefully sometime in the future, I will take a look at
potential applicability for real world needs. Until then, like many, I just
can't waste the time being an experimental lab rat with such a vital tool for
my everyday business requirements.

BCM has great potential and perhaps one of these years it will eventually get
much closer to fulfillment of such potential.

-THP

V2 to V3 migration has worked with every database and backup file I
tried it on.

Tim, do you have a file with which that's not the case?

Reading this post brings a chill to this Autumn air! With BCM 2007 getting
so close to a final release date, it amazes me that such a major feature

[quoted text clipped - 45 lines]

Message posted via OfficeKB.com
http://www.officekb.com/Uwe/Forums.aspx/outlook-bcm/200610/1

 

[Luther]

I agree users shouldn't run their businesses on beta software, and the
beta could definately message users better when they get confused or
run into trouble.

But if you are not a BCM user, what really motivates you to come here
and cast aspersions on Microsoft and the CRM tool most small businesses
use?

Luther,

I do not use BCM. Both Daniel & Coop have indicated in their posts above
that "they" have experienced migration difficulties however and this caught
my attention and motivated me to reply with my cautionary warning. BCM v. 3
is still a Beta release and to see problems from users trying to already rely
upon it for their real world business needs already is very surprising.

I will not even consider using BCM version 3 until well after the first
public version is released and then inevitably updated with numerous fixes.
This is the MS way because they dominate the software industry. Once V3 is
more established hopefully sometime in the future, I will take a look at
potential applicability for real world needs. Until then, like many, I just
can't waste the time being an experimental lab rat with such a vital tool for
my everyday business requirements.

BCM has great potential and perhaps one of these years it will eventually get
much closer to fulfillment of such potential.

-THP

V2 to V3 migration has worked with every database and backup file I
tried it on.

Tim, do you have a file with which that's not the case?

Reading this post brings a chill to this Autumn air! With BCM 2007 getting
so close to a final release date, it amazes me that such a major feature

[quoted text clipped - 45 lines]

Message posted via OfficeKB.com
http://www.officekb.com/Uwe/Forums.aspx/outlook-bcm/200610/1

 

[mrtimpeterson via OfficeKB.com]

Nice try with the attempt to label me as some kind of troll. I am motivated
to come here because I would like to be able to use BCM possibly in the
future...IF it eventually ever develops into an application that is capable
enough for such basic real world needs. I have great doubt that BCM is the
CRM tool that "most" small business use. It could be this way someday
(perhaps after version 9 released within the next decade) but is not so
currently. I lurk here and ocasionally post comments based upon a motivation
that has remained consistent even back to the days when I was a frustrated
BCM user. I would like to see BCM be made better. Constructive and honest
critical feedback makes a contribution toward that end. Overly proud labcoat
wearing programmers may bristle upon hearing such feedback about their BCM
"baby" but this app will never get better with out real world input from
discerning end users such as myself.

I have said it before that most of us do NOT have the luxury to waste time
allowing our live business to be an ongoing guneau pig with such important
needs as basic CRM.

-THP

I agree users shouldn't run their businesses on beta software, and the
beta could definately message users better when they get confused or
run into trouble.

But if you are not a BCM user, what really motivates you to come here
and cast aspersions on Microsoft and the CRM tool most small businesses
use?

Luther,

[quoted text clipped - 27 lines]

 

[Leonid S. Knyshov]

Nice try with the attempt to label me as some kind of troll. I am
motivated
to come here because I would like to be able to use BCM possibly in the
future...IF it eventually ever develops into an application that is
capable
enough for such basic real world needs. I have great doubt that BCM is
the
CRM tool that "most" small business use. It could be this way someday
(perhaps after version 9 released within the next decade) but is not so
currently. I lurk here and ocasionally post comments based upon a
motivation
that has remained consistent even back to the days when I was a frustrated
BCM user. I would like to see BCM be made better. Constructive and
honest
critical feedback makes a contribution toward that end. Overly proud
labcoat
wearing programmers may bristle upon hearing such feedback about their BCM
"baby" but this app will never get better with out real world input from
discerning end users such as myself.

I have said it before that most of us do NOT have the luxury to waste time
allowing our live business to be an ongoing guneau pig with such important
needs as basic CRM.

Tim,

You know that Microsoft reads these groups. Do you have a list of
suggestions based on BCM 2007? Beta 2TR is quite usable for my needs.
One issue is the inability to have a many to many relationship between
accounts and business contacts. The workaround for that is to use a Business
Project as a wrapper or to simply clone a Business Contact, which takes a
couple of clicks. Not ideal, but works.

I am personally pleased with the progress in BCM 2007. The mobile edition
needs a lot of love, but other than that it's usable. The performance
improvement in B2TR release vs. B2 enables me actually be able to use this
product in a VMware setting normally instead of waiting for 10 minutes for
an action to execute. I prefer to use virtual machines with multiple
rollback features when working with beta releases. SBA integration is what
makes it really cool in my mind.

I am an ISV and adding extra features may be of interest to me even if
Microsoft may take longer to implement them.
--
Leonid S. Knyshov, CEO
Crashproof Solutions, LLC - http://www.crashproofsolutions.com
MCP Exchange 2003/Small Business Server 2003
Microsoft Small Business Specialist Partner
See the tips and tricks section on my website for video tutorials on BCM
Send a smile to Microsoft (Office 2007 Beta feedback tool)!
http://tinyurl.com/m4omy

 

[mrtimpeterson via OfficeKB.com]

Leonid,

Thanks for your reply. Your posts have been fascinating and very helpful to
read. I will compile a list of suggestions based on 2007 once it is released
to the public as a production version. I am puzzled by how much discussion
occurs here in a vacuum about version 2007 as if it were already a completed
and final version for everyone to use. BCM version 3 will be available at
some unknown time next year so I cannot provide much useful feedback yet. I
was invited but declined to participate in the BCM 2007 beta because I lacked
the time necessary to devote to such an undertaking.

Your mention of the "many to many" relationship design limitation is
certainly on my list of several concerns. After 3+ years, it completely
baffles me that such basic workarounds remain necessary with BCM. Yes, there
are programming issues that can be explained technically as reasons for this
but by now, these issues could be addressed IF it were more of a focused
priority for MS to do so. The need to be able to link a contact to more than
1 account is NOT some obscure, rare scenario in the real world of any small
business. It is very common. The capability for many to many relationship
linking DOES already exist among other Outlook based, entry CRM apps. Why
does BCM still have this limitation? I have been providing consistent
feedback about this design limitation for 3 years and nothing changes. If
Microsoft reads these groups, someone obviously does not place this need high
enough among priorities to address even though it is so very fundamental to
making BCM more of a useful and versatile tool for real world usage.

Like I have stated before, I am not that overly demanding. I would like to
be able to say that I am personally pleased with the progress in BCM 2007 and
time will tell. After so many years, I just have not been able to play with
this app. as some kind of toy to be tweaked here and there. My basic user
requirements fundamentally required me to abandon BCM until future
improvements hopefully made it possible for me to consider using it again. I
would like to use a more robust and functional BCM. It does have a lot of
cool integration potential such as with SBA.

Leonid, I will try to provide constructive extra features input for you as an
ISV.

-THP

Nice try with the attempt to label me as some kind of troll. I am
motivated

[quoted text clipped - 19 lines]

allowing our live business to be an ongoing guneau pig with such important
needs as basic CRM.

Tim,

You know that Microsoft reads these groups. Do you have a list of
suggestions based on BCM 2007? Beta 2TR is quite usable for my needs.
One issue is the inability to have a many to many relationship between
accounts and business contacts. The workaround for that is to use a Business
Project as a wrapper or to simply clone a Business Contact, which takes a
couple of clicks. Not ideal, but works.

I am personally pleased with the progress in BCM 2007. The mobile edition
needs a lot of love, but other than that it's usable. The performance
improvement in B2TR release vs. B2 enables me actually be able to use this
product in a VMware setting normally instead of waiting for 10 minutes for
an action to execute. I prefer to use virtual machines with multiple
rollback features when working with beta releases. SBA integration is what
makes it really cool in my mind.

I am an ISV and adding extra features may be of interest to me even if
Microsoft may take longer to implement them.

 

[Luther]

In order to make products accessible to specific audiences sometimes
designers make decisions that other audiences disagree with.

Many small business users have trouble understanding that data is
stored in a database, let alone the possible relationships between
entities.

BCM decided that their particular schema would make it easier for
more users to use a CRM tool. Other CRM products have different
schemas or allow the user to choose their own schema.

It is similar with cars. Most people buy cars with automatic
transmissions
because the default makes it easier for them to drive. Other users
prefer stick shifts because they get better gas mileage or want more
control. There are models for both. And there are very few (zero?)
models with both automatic and manual transmissions, or user
configurable gear ratios.

I'm sure that if Microsoft saw a compelling reason to "correct" this
design limitation, they would have done so by now. Instead they are
making their bets in other areas, focusing on making other CRM
tasks easier for small businesses. In many cases that requires
making choices that will keep some businesses from adopting
BCM. Presumably, losing those customers is offset by those
they gain. SBA, intended for a similar audience, was released
after BCM and after you made your criticisms known. SBA also
decided on the same many contacts to single company schema.

To many users, the real problem is that BCM Contacts are only
intended to represent customers. BCM does not handle vendors,
employees, contractors, and other types (SBA does). For those
types, having a contact assigned to multiple accounts is a
common pattern. When BCM adds those contacts, BCM will fit with
even more users.

Whether BCM has made the right choices will be determined by
the market.

Leonid,

Thanks for your reply. Your posts have been fascinating and very helpful to
read. I will compile a list of suggestions based on 2007 once it is released
to the public as a production version. I am puzzled by how much discussion
occurs here in a vacuum about version 2007 as if it were already a completed
and final version for everyone to use. BCM version 3 will be available at
some unknown time next year so I cannot provide much useful feedback yet. I
was invited but declined to participate in the BCM 2007 beta because I lacked
the time necessary to devote to such an undertaking.

Your mention of the "many to many" relationship design limitation is
certainly on my list of several concerns. After 3+ years, it completely
baffles me that such basic workarounds remain necessary with BCM. Yes, there
are programming issues that can be explained technically as reasons for this
but by now, these issues could be addressed IF it were more of a focused
priority for MS to do so. The need to be able to link a contact to more than
1 account is NOT some obscure, rare scenario in the real world of any small
business. It is very common. The capability for many to many relationship
linking DOES already exist among other Outlook based, entry CRM apps. Why
does BCM still have this limitation? I have been providing consistent
feedback about this design limitation for 3 years and nothing changes. If
Microsoft reads these groups, someone obviously does not place this need high
enough among priorities to address even though it is so very fundamental to
making BCM more of a useful and versatile tool for real world usage.

Like I have stated before, I am not that overly demanding. I would like to
be able to say that I am personally pleased with the progress in BCM 2007 and
time will tell. After so many years, I just have not been able to play with
this app. as some kind of toy to be tweaked here and there. My basic user
requirements fundamentally required me to abandon BCM until future
improvements hopefully made it possible for me to consider using it again. I
would like to use a more robust and functional BCM. It does have a lot of
cool integration potential such as with SBA.

Leonid, I will try to provide constructive extra features input for you as an
ISV.

-THP

Nice try with the attempt to label me as some kind of troll. I am
motivated

[quoted text clipped - 19 lines]

allowing our live business to be an ongoing guneau pig with such important
needs as basic CRM.

Tim,

You know that Microsoft reads these groups. Do you have a list of
suggestions based on BCM 2007? Beta 2TR is quite usable for my needs.
One issue is the inability to have a many to many relationship between
accounts and business contacts. The workaround for that is to use a Business
Project as a wrapper or to simply clone a Business Contact, which takes a
couple of clicks. Not ideal, but works.

I am personally pleased with the progress in BCM 2007. The mobile edition
needs a lot of love, but other than that it's usable. The performance
improvement in B2TR release vs. B2 enables me actually be able to use this
product in a VMware setting normally instead of waiting for 10 minutes for
an action to execute. I prefer to use virtual machines with multiple
rollback features when working with beta releases. SBA integration is what
makes it really cool in my mind.

I am an ISV and adding extra features may be of interest to me even if
Microsoft may take longer to implement them.

 

[Leonid S. Knyshov]

Leonid,

Thanks for your reply. Your posts have been fascinating and very helpful
to
read. I will compile a list of suggestions based on 2007 once it is
released
to the public as a production version. I am puzzled by how much
discussion
occurs here in a vacuum about version 2007 as if it were already a
completed
and final version for everyone to use. BCM version 3 will be available at
some unknown time next year so I cannot provide much useful feedback yet.
I
was invited but declined to participate in the BCM 2007 beta because I
lacked
the time necessary to devote to such an undertaking.

Your mention of the "many to many" relationship design limitation is
certainly on my list of several concerns. After 3+ years, it completely
baffles me that such basic workarounds remain necessary with BCM. Yes,
there
are programming issues that can be explained technically as reasons for
this
but by now, these issues could be addressed IF it were more of a focused
priority for MS to do so. The need to be able to link a contact to more
than
1 account is NOT some obscure, rare scenario in the real world of any
small
business. It is very common. The capability for many to many
relationship
linking DOES already exist among other Outlook based, entry CRM apps. Why
does BCM still have this limitation? I have been providing consistent
feedback about this design limitation for 3 years and nothing changes. If
Microsoft reads these groups, someone obviously does not place this need
high
enough among priorities to address even though it is so very fundamental
to
making BCM more of a useful and versatile tool for real world usage.

Like I have stated before, I am not that overly demanding. I would like
to
be able to say that I am personally pleased with the progress in BCM 2007
and
time will tell. After so many years, I just have not been able to play
with
this app. as some kind of toy to be tweaked here and there. My basic user
requirements fundamentally required me to abandon BCM until future
improvements hopefully made it possible for me to consider using it again.
I
would like to use a more robust and functional BCM. It does have a lot of
cool integration potential such as with SBA.

Hi Tim,

The reason for us treating the product as if it's final at this stage is
because we have no reason to anticipate any major changes from this point
forward prior to the initial Office 2007 release next year. We anticipate
incremental improvements and better exception handling, but nothing major.
SBA 2007 beta period ends on October 31. Shortly after, it will be the first
released product of the Office 2007 generation. Its last release was B2TR. I
would strongly encourage you to try the B2TR release. It's a wide beta
release without formal surveys, although sometimes I wish bug reports were
tracked via Connect as SBA beta was. I think we would have a better product
that way, but Microsoft got a lot of feedback from bug reports in the groups
as well.

I do not see any show-stopper issues with Office 2007 B2TR in my daily use
and some of my customers have it deployed now in production. Their support
costs from us have not increased since that point, so it's working fine for
them.

Luther makes a great point about using SBA 2007 to track many to many
relationships. I think he's hitting it correctly that BCM needs to be
extended to encompass that functionality.

Microsoft has in the past accelerated point releases of SBA and BCM, so we
hope to see more improvements over the next few years.

As it is right now, however, it's already a great product.
--
Leonid S. Knyshov, CEO
Crashproof Solutions, LLC - http://www.crashproofsolutions.com
MCP Exchange 2003/Small Business Server 2003
Microsoft Small Business Specialist Partner
See the tips and tricks section on my website for video tutorials on BCM
Send a smile to Microsoft (Office 2007 Beta feedback tool)!
http://tinyurl.com/m4omy

 

[mrtimpeterson via OfficeKB.com]

[Leonid wrote: Luther makes a great point about using SBA 2007 to track many
to many
relationships. I think he's hitting it correctly that BCM needs to be
extended to encompass that functionality.]

Regardless of any reasons that each of us can speculate over why BCM remains
the way it is, this is still a false choice and entirely unnecessary after
all of these years. This built in limitation that restricts users from
linking more than 1 account to a business contact is just plain stupid. I
would like to see how the market responds if prospective users know upfront
of this limitation vs. sadly discovering it later after they go to the
trouble of loading the software and begin to use it. If this is such an OK
thing strategically chosen by MS, then they should publish a clearly
disclosed notification of this upfront.

Something like the following in writing would do quite nicely:

NOTICE TO ALL POTENTIAL 2007 BCM USERS. IN CONTRAST TO ALMOST ALL OTHER
ENTRY CRM OPTIONS AVAILABLE FOR YOUR CONSIDERATION IN TODAY'S MARKETPLACE,
THE USE OF BCM 2007 WILL REQUIRE YOU TO ADAPT AND RESTRICT THE RECORDING OF
YOUR BUSINESS RELATIONSHIP DATA WITHIN A BUILT-IN LIMITATION OF THIS PRODUCT
DUE TO OUR INTENTIONALLY DESIGNED, "ONE-TO-MANY" VS. "MANY-TO-MANY" FEATURE
SET. WE ARE MOST PROUD OF THIS NEW "STATE-OF-THE-ART" PRODUCT FEATURE SO
PROCEED ACCORDINGLY.

As long as we are back to using car analogies again, I will dust off my old
favorite. Trying to use BCM for my real world business with this "1 to many"
built in limitation is NOT a fickle choice between an automatic vs. manual
transmission. It is more like choosing a car with or without something as
basic as a steering wheel being included. Or, more precisely, it is like
there is a transmission in the car but it lacks reverse everyone. Hey, no
big deal out there. We are carefully targeting this car to certain users
knowing full well that we won't please everyone. Those picky folks who
absolutely require reverse can just go elsewhere for their car. Just give us
a few more years here and we'll get around to including reverse in this baby.
Other than that everyone, this new BCM is a really great car with all kind of
fancy bells and whistles and wizards, etc.

To each their own I guess. Folks will likely have to just check back in a
few more years when MS is motivated to correct this basic flaw rather than
attempt to apologize or explain away this oversight with more fancy target-
marketing nonsense as excuses.

-THP

Leonid,

[quoted text clipped - 47 lines]

would like to use a more robust and functional BCM. It does have a lot of
cool integration potential such as with SBA.

Hi Tim,

The reason for us treating the product as if it's final at this stage is
because we have no reason to anticipate any major changes from this point
forward prior to the initial Office 2007 release next year. We anticipate
incremental improvements and better exception handling, but nothing major.
SBA 2007 beta period ends on October 31. Shortly after, it will be the first
released product of the Office 2007 generation. Its last release was B2TR. I
would strongly encourage you to try the B2TR release. It's a wide beta
release without formal surveys, although sometimes I wish bug reports were
tracked via Connect as SBA beta was. I think we would have a better product
that way, but Microsoft got a lot of feedback from bug reports in the groups
as well.

I do not see any show-stopper issues with Office 2007 B2TR in my daily use
and some of my customers have it deployed now in production. Their support
costs from us have not increased since that point, so it's working fine for
them.

Luther makes a great point about using SBA 2007 to track many to many
relationships. I think he's hitting it correctly that BCM needs to be
extended to encompass that functionality.

Microsoft has in the past accelerated point releases of SBA and BCM, so we
hope to see more improvements over the next few years.

As it is right now, however, it's already a great product.

 

[Luther]

I guess we won't hear from you for a few more years then. Bye.

[Leonid wrote: Luther makes a great point about using SBA 2007 to track many
to many
relationships. I think he's hitting it correctly that BCM needs to be
extended to encompass that functionality.]

Regardless of any reasons that each of us can speculate over why BCM remains
the way it is, this is still a false choice and entirely unnecessary after
all of these years. This built in limitation that restricts users from
linking more than 1 account to a business contact is just plain stupid. I
would like to see how the market responds if prospective users know upfront
of this limitation vs. sadly discovering it later after they go to the
trouble of loading the software and begin to use it. If this is such an OK
thing strategically chosen by MS, then they should publish a clearly
disclosed notification of this upfront.

Something like the following in writing would do quite nicely:

NOTICE TO ALL POTENTIAL 2007 BCM USERS. IN CONTRAST TO ALMOST ALL OTHER
ENTRY CRM OPTIONS AVAILABLE FOR YOUR CONSIDERATION IN TODAY'S MARKETPLACE,
THE USE OF BCM 2007 WILL REQUIRE YOU TO ADAPT AND RESTRICT THE RECORDING OF
YOUR BUSINESS RELATIONSHIP DATA WITHIN A BUILT-IN LIMITATION OF THIS PRODUCT
DUE TO OUR INTENTIONALLY DESIGNED, "ONE-TO-MANY" VS. "MANY-TO-MANY" FEATURE
SET. WE ARE MOST PROUD OF THIS NEW "STATE-OF-THE-ART" PRODUCT FEATURE SO
PROCEED ACCORDINGLY.

As long as we are back to using car analogies again, I will dust off my old
favorite. Trying to use BCM for my real world business with this "1 to many"
built in limitation is NOT a fickle choice between an automatic vs. manual
transmission. It is more like choosing a car with or without something as
basic as a steering wheel being included. Or, more precisely, it is like
there is a transmission in the car but it lacks reverse everyone. Hey, no
big deal out there. We are carefully targeting this car to certain users
knowing full well that we won't please everyone. Those picky folks who
absolutely require reverse can just go elsewhere for their car. Just give us
a few more years here and we'll get around to including reverse in this baby.
Other than that everyone, this new BCM is a really great car with all kind of
fancy bells and whistles and wizards, etc.

To each their own I guess. Folks will likely have to just check back in a
few more years when MS is motivated to correct this basic flaw rather than
attempt to apologize or explain away this oversight with more fancy target-
marketing nonsense as excuses.

-THP

Leonid,

[quoted text clipped - 47 lines]

would like to use a more robust and functional BCM. It does have a lot of
cool integration potential such as with SBA.

Hi Tim,

The reason for us treating the product as if it's final at this stage is
because we have no reason to anticipate any major changes from this point
forward prior to the initial Office 2007 release next year. We anticipate
incremental improvements and better exception handling, but nothing major.
SBA 2007 beta period ends on October 31. Shortly after, it will be the first
released product of the Office 2007 generation. Its last release was B2TR. I
would strongly encourage you to try the B2TR release. It's a wide beta
release without formal surveys, although sometimes I wish bug reports were
tracked via Connect as SBA beta was. I think we would have a better product
that way, but Microsoft got a lot of feedback from bug reports in the groups
as well.

I do not see any show-stopper issues with Office 2007 B2TR in my daily use
and some of my customers have it deployed now in production. Their support
costs from us have not increased since that point, so it's working fine for
them.

Luther makes a great point about using SBA 2007 to track many to many
relationships. I think he's hitting it correctly that BCM needs to be
extended to encompass that functionality.

Microsoft has in the past accelerated point releases of SBA and BCM, so we
hope to see more improvements over the next few years.

As it is right now, however, it's already a great product.

 

[mrtimpeterson via OfficeKB.com]

Oh, I'll be around every now and then. After all, someone needs to provide a
factual reality check to counter the BCM cheerleading spin that sometimes
occurs here.

-THP

I guess we won't hear from you for a few more years then. Bye.

[Leonid wrote: Luther makes a great point about using SBA 2007 to track many
to many

[quoted text clipped - 74 lines]