Yup, ACT chokes on a specific record and in fact, it's # 26, so how's the
best way to identify record # 26? Besides the company, is it then sorted by
last name? I guess I'm wondering if there is a corrupt record, why doesn't
ACT fix it when doing the "fix & repair" utility?
Thanks,
Dino
Lon Orenstein said:
Luther's right but there's a caveat. Record number 26 is not necessarily
#26 in the list you see on screen -- it's #26 that is stored in that
position in the database. The list is usually sorted by Company...
___________________________________________________________
Lon Orenstein
pinpointtools, llc
(e-mail address removed)
Author of Outlook 2007 Business Contact Manager For Dummies
Author of the eBook: Moving from ACT! to Business Contact Manager
www.pinpointtools.com
I did this on my personal computer with no problem, work computer seems to
present the problem where BCM chokes on the import. It looks like it
starts
importing the contacts, gets to about 26, and stalls.
Have you seen that before?
"William Stacey [C# MVP]" wrote:
Not sure if this helps, but I just imported other day from an act 6 dbf
directly into BCM with no issues (I installed trial ACT 10 on machine
first).
IIRC, BCM will import directly from act 10 .pad db. Can't remember if I
tried that also or not.
I'm trying to import information from ACT 10 into Business Contact
Manager.
Does anyone know of a template for this? - I can't seem to find one
from
Microsoft.
Do I have to do my own import? and if so, can I start with an ACT 9
template? I tried using the Act 2007/9 template to import, but that
fails
during the conversion...
Dino- Hide quoted text -
Usually, when conversion from ACT to BCM gets to record number N and
stops, it's an indication that record N is corrupt. Deleting the
offending record from ACT usually helps--import continues past that
point.- Hide quoted text -
- Show quoted text -
A couple years ago I was involved in debugging an application that got
its data from the then current ACT 6 or 7 release. They had one
database where my code would connect to the ACT API, connect to the
contacts table, ask for the first record, and then loop asking for the
next record. It would then get hung on one particular record. I
attached a debugger and there was a cast exception inside the ACT
stack. If my code tried disconnecting and reconnecting back to ACT, it
would get corrupt memory exceptions. The only way to get ACT to
respond was to restart the process. When the next relese of ACT came
out, it had exactly the same problem with the same database. They
should, but I wouldn't wait for ACT to fix the problem.