Importing ACT ver 7 to BCM 2007

[RSA07-mm]

We purchased 2007 Ultimate, but I am currently running a trial version while
our copies are being shipped. We currently use ACT ver 7.0.4.82 and would
like to migrate to BCM. Outlook appears to have a migration wizard, but it
does not work. We get error "The specified file is not a vaild database for
the currently installed version of ACT (7). If the file is a database from a
prior ACT version, it can be upraded by opening the database in ACT."
Guranteed, the file I have selected to migrate is a current database. What's
the problem?

I called MS pre-sales (don't have my valid copy yet) and get mixed stmts
(trial version has limited capabilities) - is this true? I read the
postings on BCM here and have a growing feeling that I am facing an avalanche
of problems by upgrading. When I was lucky enough to be assigned a support
case with MS, the tech was not able to help me because of newness of product
and lack of trainning. My company is small, but we're still looking at
spending over $6k to upgrade.

Really, can BCM import ACT 2005 ver 7 database? Is it stable? What's the
story on BCM sluggish performance (We have that with ACT on new core 2 pcs
and want to get rid of problem)? Any other current users have comments for
or against office 2007?

 

[Bob Cooley [MS]]

Yes, BCM can import ACT! 7.0. files

BCM looks for two things when importing from ACT!:

- ACT! must be installed on the same machine as BCM
- The file extension must match the version of ACT! chosen in the Migration
Wizard - the extension for the ACT! 7.0 files are .PAD.

Hope this helps!

Regards,

Bob Cooley, MSFT

 

[James]

Bob,

That isn't all it needs because we are having the same problem and have
exactly what you just listed here. The only thing i can see possibly causing
the problem is that ACT is version 7.04.82 and the database is version
7.04.75.

So again the question needs to be asked what else is needed to complete this
task which has been labeled as being so simple?


James

 

[Luther]

Bob,

That isn't all it needs because we are having the same problem and have
exactly what you just listed here. The only thing i can see possibly causing
the problem is that ACT is version 7.04.82 and the database is version
7.04.75.

So again the question needs to be asked what else is needed to complete this
task which has been labeled as being so simple?

James








- Show quoted text -

Usually 3rd party tools have problems accessing ACT is the database
version doesn't match the software. If you open the database is ACT
7.04.82 and save some data, does the database version get bumped up to
7.04.82?

 

[RSA07-mm]

Similiarly, our Act vs is 7.04.82 and our database product version reads as
8.00.818-SP3. I'm guessing that there is little relation between the
database version and the Act version. If Microsoft is relying on the two
versions to be the same in order for the conversion wizzard to work, it
appears they're catering to a small, rare market. Are my thoughts off base?

We downloaded a 50-60 page document written by Lon Orenstein (ie. Converting
Act to BCM for Dummies). We have hired an outside IT guru to come in and
hopefully convert our database - $$$. So, does the conversion wizzard work?
Only if you're an IT guy for hire.

 

[Luther]

Similiarly, our Act vs is 7.04.82 and our database product version reads as
8.00.818-SP3. I'm guessing that there is little relation between the
database version and the Act version. If Microsoft is relying on the two
versions to be the same in order for the conversion wizzard to work, it
appears they're catering to a small, rare market. Are my thoughts off base?

We downloaded a 50-60 page document written by Lon Orenstein (ie. Converting
Act to BCM for Dummies). We have hired an outside IT guru to come in and
hopefully convert our database - $$$. So, does the conversion wizzard work?
Only if you're an IT guy for hire.






- Show quoted text -

From ACT->BCM issues in the past...I think that BCM uses ACT's SDK to

get the data from ACT, instead of going to the ACT database directly.
And if the ACT database and software versions don't match, then the
calls to the ACT SDK return errors.