Upgrade to ACT 2007 and adding a remote user

[MadelineBasset]

Hello. We used to have single-user Act! 2005, but have recently needed to upgrade to Act 2007. We purchased three licenses. Two users will work in the office, but one user will be working from home. Is it possible to keep the Act! database on a web server and sync it that way?

Thank you very much for your help.

 

[GLComputing]

Web sync (IIS) is only possible with the Premium or Workgroup versions of ACT!9 (2007). For Standard ACT! 9, you can set up a VPN and sync across the 'net that way

Regards,
Mike Lazarus
ACT! Evangelist
GL Computing, Aust

http://www.GLComputing.com.au

For ACT! by Sage and ACT! for Lotus Notes

 

[boulderjamie]

Wonder if anyone has ever seen "Object reference not set to an instance of an object" error message. I have just transfered ACT to my Desktop computer and imported my database into a new database I created on my desktop. I get this error when I try to use the telephone dialer. I have tracked down that it may be a .NET error, but I have no idea how to fix it. Ideas?

Jamie

 

[GLComputing]

The exact meaning will depend on the version of ACT!, and exactly what you click to cause it. Searching the ACT! knowledge base will usually get you the correct answer, like

http://itdomino.act.com/act.nsf/docid/13786

Regards,
Mike Lazarus
ACT! Evangelist
GL Computing, Aust

http://www.GLComputing.com.au

For ACT! by Sage and ACT! for Lotus Notes

 

[boulderjamie]

Thanks for this link to the Knowledge Base. I had tried searching ACT website but obviously wasn't in the right place. I didn't solve the problem in the way recommended in the article, but it gave me an idea and since you list yourself as an ACT evangelist I thought you might be interested in the solution.

I tried dialing different contact and the error didn't reappear. When I was testing and trying to fix this I had been dialing only two contacts, the two I had entered most recently. I tried them again and voila the error reappeared. In trying to fix this I had created new databases, imported the old database, tried it again with different options. Problem is, after I did this I tested on the two records that were giving me problems, so the problem must have carried through the import process.

To solve I just went into these two records and deleted their phone numbers, saved the contact record, entered phone numbers again, saved and the dialer now works fine. Just after entering these records, I must have tried to dial these two records before saving. Not really a technical solution, but raises interesting thoughts about what is saved in the phone fields of these records to cause the error and the fact that it is carried through imports.

Jamie

 

[GLComputing]

Glad you got it working... the wonders of databases

To be honest, I prefer this add-on for dailing -

http://www.glcomputing.com.au/main.php?prodid=56&s=1

It also does much more including incoming CallerID, better History, Skype (both calls and SMS), etc. Well worth it if doing a fair bit of phone work.

Regards,
Mike Lazarus
ACT! Evangelist
GL Computing, Aust

http://www.GLComputing.com.au

For ACT! by Sage and ACT! for Lotus Notes

 

[boulderjamie]

Thanks. Will take a look at that when I have a free minute. I am scrambling to make up for the time I lost trying to finesse this baby into working right. Gotta love em (databases)!

 

[GLComputing]

Madeline, I forgot to mention that you can also use the Premium for Web version and have the remote user operate in real time with you.

Regards,
Mike Lazarus
ACT! Evangelist
GL Computing, Aust

http://www.GLComputing.com.au

For ACT! by Sage and ACT! for Lotus Notes