Act Tech Support Webinar: Click Here to Register
You probably love a good mystery – but not when it comes to your Act database! If you’re like most Act users you rely on Act to run your business and when your Act starts “acting up” panic sets in.
I receive dozens of calls and emails a week from Act Users who are in need of Act tech support. Ironically, most of the calls center around a set of core issues that are quite easy to fix.
The Virtual Act Users Group will be holding an Act Software Webinar on Tuesday, April 18 at 12 PM EST. The webinar is designed as a DIY tool to help you fix over a dozen of the most common Act issues and save you hours of troubleshooting time. All registrants will be receiving a recording of the presentation in case you can’t attend the live presentation or want to refer to it later.
I’m also giving you a free copy of the“Fix Phone Formatting ” utility that will scour through every phone number in your database and correct the ones that have extra spaces, improper parentheses and/or invalid characters. This product retails for $79 and can save you hours of time.
Prior registration is required; click here to register.
Now that I have my version of ACT! up to date and can once again able to do a complete backup, I will be loading a lot of new contacts from spreadsheets. I have a question about this.
Should I put all contacts into one database – estimate 1000-1500 active accounts and another 20K leads? And is there any practical limit to the number of contacts? I’ve tried to find some writing on this but haven’t yet.
My thoughts is it may be better to have a separate leads database or two…
Use same layout/fields for all databases so when I move a lead to my active database, all info is transferred. I may be totally wrong on this and just looking for an opinion.
With SQL databases size is based on a number of factors – number of notes, histories, customized fields – as well as the number of contacts. And performance is based on your hardware – RAM, hard drive speed, processor. I have many clients with over 100K of contacts. For me, it’s a pain to have to keep multiple databases as you’d have to deal with multiple calendars, maintenance and just moving between them constantly. I’d put them all into one database and perhaps move out old ones periodically into an archival database.