Pervasive

Hello,

First of all, i'm no database expert, here is the situation.

We are using a medical program which needs pervasive. We have 3 workstations with pervasive installed and a pc with windows 7 installed that stands alone that holds the database (pervasive not installed).

Initially the PC that held the database was windows xp, which gave no problems.

However, now that we have windows 7 installed, when we want to launch the program it goes much slower, afterwards everything goes much faster.  It is almost as if when we start our program it takes a lot of time to connect to our "server".

Anything that is known about this isue?

Please bear with me while I try to see if I understand the setup.

Your Windows 7 computer has Pervasive data files, but does not have Pervasive installed, right?

You have 3 other computers with Pervasive installed (I assume Workgroup Engine) and they all access the data files on the Windows 7 computer.  Are they accessing them through a mapped drive?

Did the previous XP machine have Pervasive installed?

 If your machines have Workgroup Engine, can you tell me if they are installed as an Application or Service?  The best way to check is to look in Services.  If there is a Pervasive Workgroup Service, then it's installed as a service.  If not, there should be a small icon near the clock that looks like a blue cylinder.

If you could also check the folder where the data files reside.  When people are accessing the data, if it's through workgroup, there should be a file called ~pvsw~.loc.  If you open the file in Notepad, you will see the name of the computer who is acting as the Database Engine.

Thanks

 Sounds like the "long time to connect" and once connected performance is fine.  Actually since there is no engine on the target the connect time may be long while the initial timeout happens.

  In the client setting in PCC you may want to briefly turn on the "Gateway Durability" setting so that it registers you new "server" as not having a database engine running.  Afterwards they will skip attempting to connect to a database engine because it will remember there is not one.  It is usually a good idea to turn the setting back off lest it remember one of the other machines that does have an engine as not having one due to it being turned off or some other temporary event.