12-02-2008 09:58 AM
12-02-2008 11:25 AM
1. Is ACT! registered on the personal computer?
2. Have you tried running ACT! as an administrator (right click ACT! icon > Run as Administrator)?
3. Is there only one user created in the database?
12-15-2008 01:08 PM
I used the "import" command which will merge (with a few duplications) 2 different data bases with the same name. There are filters and parameters you can set before you initiate the import operation. These are intended to avoid dupes. Most of it worked fine. The restore scheme never worked properly - I think it's primarily for backing up a data base then reviving it.
02-02-2009 02:29 PM
Another flavor of the same problem. As mentioned below, I was able to successfully import my data into the original computer and update the data base successfully. I now have yet another new computer (one was a company machine, then I changed jobs and want to mount it on a new company machine) and am now having a different issue trying to resolve the same problem. When I try to open the data base file that I transferred to the new computer I get the following "The database <name> could not be accessed. In order to access this database, check your network connection and verify that your database server is availaible. It may be necessary to disable any firewall software on your computer or the server." It still gives me this when I turn the firewall off.
What's weird about this though is that I have imported all the data to a local drive so there is no server or firewall involved.
When I try importing the old data into a newly named file I get a simple ""Error in the application."
This is extremely frustrating. Anybody have any ideas?
02-06-2009 02:17 PM
I had a similar problem and learned you can NOT just "copy" the database files from one machine to another.
The SQL stuff is bound to the machine name, so you should do
a backup incl. Attachments on the old machine
and a restore "with a new name" on the new PC.
This will behave as if the database was created with the SQL machine/user settings on the new PC...
Another strange behavior found is that "ghosting" aka image-transfer a PC with installed ACT will also give hickups.
The SQL group accounts and many registry settings will retain the old machine name, even if the machine is renamed after the image transfer.
the utility NEWSID (useful to rename / renumber a image copy) will not rename the SQL parameters (maybe there will a very
fresh NEWSID later that will recognize an installed SQL 2005). As quick-&-dirty repair we asked our ACC programmer to write
a small script that does a global replace in the registry keys old-machine-name -> new-machine-name (which worked in our case
as all new machines were generated from one image - where we actually knew the old-machine-name). Nothing for the faint-hearted...
Hope that helps.