Quote from runner1717 on 05/16/08 at 08:41:34:You are correct. It's a client / server installation.
I don't have to deal with the DBA installation very often. In a client / server installation is there a client install of DBA and/or Pervasive to the client or do I just make a shortcut to the DBA executable on the server?
The installation was working fine. Now it's not. Could the error 11 be drive LETTER oriented?
Thanks,
Mike
You need the client version of PervasiveSQL on the client. Then you map a drive letter (doesn't matter what it is) and create a link directly to the DBA executable. At least, you can do that in DBA Classic. In Evo you run the evoerpsetup program from the server and it sets up a local C:\ISTS folder on the client.
I am unaware of any problem if the drive letter to DBA changes. At least, so long as it does not change while the program is running. Especially if you use C/S because then all data files just stay on the server and the drive mapping doesn't matter.