Community
Showing results for 
Search instead for 
Do you mean 
Reply

Cannot upgrade even Act6Demo database to V18

Copper Contributor
Posts: 11
Country: Australia

Cannot upgrade even Act6Demo database to V18

I am in the process of evaluating ACT! V18 Pro. We have used ACT! v6 for years.. decades, even, upgrading from the previous version a long time ago.

 

My first step was to try to update out own Database. Quite heavily customised, 7,500 contacts or thereabouts. It didn't work. I got the dreaded "pre7actdb.adb" error.

 

ACT database upgrade 6.JPG

 

Reading up on this error, I read about whole bunch of possible solutions. So I thought "Maybe it is because my customisations are too complicated" so I decided to try to convert the "untouched" default Act6Demo database. Hello, Chris Huffman ... long time no see.

 

I did all the right things. The test DB is local - not on a  network. I saved it via "Create a Copy".

I ran the actdiag.exe file and got a clean sweep of green ticks, after re-indexing the database.

 

ACT database upgrade 9 - actdiag- OK.JPG

 

Still no go.

 

I'm using Windows 7 Pro, 64 bit.

 

What on earth could be the matter? I can't even convert the simple demo database, let alone attempting to convert my own one.

 

I hope someone can assist me! I'd really like to get started using ACT! 18.

 

Administrator
Posts: 4,024
Country: United_Kingdom

Re: Cannot upgrade even Act6Demo database to V18

Hi sKraeL,

If you are currently running a v18 trial, we should be able to help you with this. I would suggest calling our Technical Support team on +61 (0)3 9111 0500.
Sometimes v6 databases need an intermediary upgrade step before being updated to the most recent Act versions.
Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Cannot upgrade even Act6Demo database to V18

Tech support will usually upgrade databases to the current version for free ...
Unless there's an issue with your installation. In which case, you might try contacting a local Act! Consultant.
Copper Contributor
Posts: 11
Country: Australia

Re: Cannot upgrade even Act6Demo database to V18

Thanks for the reply, Gary. I tried to call about this from Australia.

 

However, due to a mandatory public holiday in India, I am not able to get technical support in Australia today, according to the answering machine message.

 

I will call India again tomorrow to see if the customer support team can assist me further.

Copper Contributor
Posts: 11
Country: Australia

Re: Cannot upgrade even Act6Demo database to V18

Mike, when (if) it gets to that stage can I buy ACT! pro 18 from you?

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Cannot upgrade even Act6Demo database to V18

Copper Contributor
Posts: 11
Country: Australia

Re: Cannot upgrade even Act6Demo database to V18

I decided to give the conversion attempt one more try. Frankly, I was a bit uncomfortable sharing my database with others, and the idea I have to deal with an Indian-based support centre made me more wary. All unjustified perhaps, not like I have such super-secret contact information but still.....

 

So in the interest of sharing/contributing to the community, I have the following suggestion for others attempting this same transition, although how many users are still using ACT! 6? Cannot possibly be THAT many by now, surely.

 

There was an interim step needed for the database conversion, I had to FIRST convert the database using ACT! v12, THEN convert the resulting database to ACT! v18.

 

I located the trial version of V12 here:

http://keystroke.ca/default.asp?pID=49#.VzvcguTK1I5

 

There was a bit of initial hassle, as I had to first uninstall ACT! 18 as well as uninstalling the SQL server. However, after this the conversion went fine, as did converting over the custom layout (with some minor work still to be done)

 

The next step is to convert over a few more custom fields and tweaking the layout further. The following resources might help others with this same query:

I have yet to finalise the conversion properly. I will have to repeat the procedure after reading the 2 guides above so I can properly map over all of my custom fields somehow.