Link to home
Start Free TrialLog in
Avatar of sexygeek
sexygeek

asked on

Is there a problem using Windows 7 as a shared ACT! 2010 database?

I'm trying to connect two users to an ACT! 2010 database over a network.  There was no problem with this database until the user of the PC used as the ACT! database server upgraded to 32-bit Windows 7.  He did a clean install of 7 and then reinstalled ACT! 2010 (2010 is what he had running and what the other users are running.)  The old users show up in the database and the database is set for Sharing on the network.  In addition, I shared the folders and gave read/write and execute permissions to Everyone.  I can log into his computer from the other computers (one is Windows 7 and the other is Vista) and see the .PAD file.  However, even if I click on the .PAD file directly, I get the same time out and ACT! says I can't access the resource.

Do I need to set permissions for some other folders?  This all worked fine when the user was running it on XP.

Any help would be appreciated!  (By the way - I couldn't find the ACT! zone when adding this)
Avatar of Mike Lazarus
Mike Lazarus
Flag of Australia image

What's the exact error?

Can you try deleting the PAD file on the host machine and the (from ACT!) - File | Open ... change File Type to ADF ... and open it
This will create a new PAD file
Avatar of sexygeek
sexygeek

ASKER

I'll try that when I get in there tomorrow.  Come to think of it, why is it that I can see the .ADF file from the "server" PC when logged in locally but can't see it from across the network (using the local user's login?)  Actually to be fair, I'll post this as another question right now!)
BTW: here's the ACT! zone: https://www.experts-exchange.com/Database/Contact_Management/ACT/

You can open the PAD file in Notepad ... this will show the Server machine name, Path to the database and Database name
I know I have the right PAD file because I can open the database with it locally even if I move it to another folder.  As long as I double-click on it, the DB opens.  A search of all PAD files reveals no one excpet this one created any later than 2009.  

OK, I removed the .PAD file as suggested above and started ACT!, 2010.  The program opended with the following dialog:

         THe last database opened could not be located.

The browse window came up and I browsed back to the database location, changed the file type to ADF and attempted to start the ADF file of the same name.  The error returned:

        nameoffile.ADF
        This file is in use
        Enter a new name or close the file that's open in another program.

I could locate no other program that has this file open including Explorer, so I resarted only to get the same error.
Open ACTDIAG and detach the ACT! database, then try again ...
Yes thanks, after detaching the DB I was able to generate a new PAD file.  However, I still can't start the DB from another PC.  Whether I use the PAD file on the remote machine or I browse using Windows Explorer and double-click on the server PAD file, I get this error:

       The database mydbfilename could not be accessed.
       In order to access this database, check your network
       connection and verify that your database is available.
       It may be necessary to disable any firewall software
       on your computer or the server.

I can tell you that I've turned off Kaspersky on ther server and the other machine.  Obviously, if I can open the network share on the server, connection is not an issue.
ASKER CERTIFIED SOLUTION
Avatar of Mike Lazarus
Mike Lazarus
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you.  These both look very promising.  I'll report back tomorrow.
Unfortunately, there isn't a shortcut for that error unless it was working and something changed to stop it.

It just means that it can't connect and doesn't really know why.

So you just try each of the items, one at a time, and check to see if the other machines can open it after each try
How are you going with this?