Sounds lika a Pervasive issue. Did the Pervasive install and database tests go good. Maybe try uninstalling and reinstalling pervasive again?
 
John

Is this workstation a Win XP? Pervasive 2000 is a very old version. I think XP has some issues with it and some do not. You could try to update your Pervasive. You can still download 2000I or it might be on your DBA CD.
 
http://www.pervasive.com/support/updates/psa_update.asp
 
This is a link to a utility to trouble shoot 2000.
 
http://www.pervasive.com/support/updates/2000i_sp4.asp
 
This is a link to the 2000I SP 4 build 251. It has solved many issues for me.
 
John

Have you mapped a drive to the PVSW folder?  Then the path is just the mapped drive, without PVSW.  
 
Also, is this person new, and if so have you given him the correct permissions to the DBA and PVSW folders?

Thanks for all your advice,  I know it is a valuable resource for the ARCHIVES  (which I search on a regular basis)
 
On the Dell I installed 3 weeks ago, I had removed all of Dells pre-installed junk, i.e. Qbooks and AOl and netzero, etc.  and all the millions of trial versions.  
 
But I had not removed all the "junk" on this new DELL.
Once the junk was removed it worked.  
 
Laura

Your problem with the Dell reminds me of the early days of DBA ( W98 and first version of DBA)when we had all Dell machines, and there was a big conflict going on with just two of the newest ones, which took hours of DBA and Dell and Network tech time to figure out. (All pointing fingers at the other guy!)  I don't remember what Dell files I got rid of, but it fixed the problem then too.
 
Glad you found the problem!

We don't run Dells, but on other "preconfigured" machines I've killed all the extra, non-business stuff installed.  We mostly buy only business (vs consumer) machines so it's rare I have to deal with that, except for Dell.  We do run McAfee on all our machines and have never had a problem running DBA or EvoERP, ever.
 
One thing I learned on the XP machines--edit the hosts file and put in an entry for the server if you ever see the tests failing.  It always works!  XP just seems to need it whereas a Windows 2000 machine typically does not.
 
Val

you are supposed to install pervasive client TO the local computer C:\pvsw and start the install FROM the server's pvsw\client folder.  
 
the Testing during the local client install wants to test the pervasive engine, of which THEN you point to the server's pvsw\sample folder.
 
it sounds like your F: drive is pointing to the server's drive which allows you access to the stuff there.
 
however, if you installed the client back to the server.... that' causes problems for pervasive on the server as well as dba/evo. i hope that's not what you did.