BCM 2003/2007 Compatibility

[Guest]

My office has 3 new CPUs running BMC 2007, and they use an older CPU as a
"server"(really just shared files on a central desktop.) I wanted to use the
contacts from the central desktop, which has BMC 2003 (updated), but after
setting up the users with access to the database, my user CPU says that I
failed to input the correct password. I know I've typed it correctly. I've
changed the guest user login password to match the BMC password, no help.
I've allowed each IP add. for outlook in the firewall settings, no help. I
can ping each machine from "server," but I'm against a wall. Am I trying
something that's impossible, or am I missing something?

In an office with 4 people, the guy that knows more that MSWord is the I.T.
guy...

 

[mrtimpeterson via OfficeKB.com]

BigLee,

Someone else more in the know on this forum will have to confirm because I
could be in error, but I do not believe that you are missing something. What
is likely missing is that BCM 2003 is not compatable to network with BCM 2007.
Surprise, MS strikes again! Your problem likely stems from the attempt to
cross configure between these 2 different versions.

-THP

 

[Luther]

BigLee,

Someone else more in the know on this forum will have to confirm because I
could be in error, but I do not believe that you are missing something. What
is likely missing is that BCM 2003 is not compatable to network with BCM 2007.
Surprise, MS strikes again! Your problem likely stems from the attempt to
cross configure between these 2 different versions.

-THP

BCM will only work databases that are the same version. When BCM
connects to an earlier version database, it should prompt you upgrade
the database to the current BCM's version. However, I suspect that
will only work for the database owner--not other shared users--and,
after upgrading, older versions of BCM will no longer connect to that
database.

 

[Guest]

Yup, its not asking you to upgrade the database because it can't. BCM V2 is
as high as you can go without switching to outlook 2007. If you were to
browse to the default location for the sql files (I don't know why anyone
would want to really) but youd see that the .mdf and .ldf files are now
listed as a transaction log file and primary data file, V2 cannot see em.