>I developed and application that accesses DacEasy data, which is in a Pervasive (btrieve) data base. In the previous version of DacEasy data was accessed via a local engine which got it directly from the files in the server, much like VFP does. The application used remote VFP views to access the data and I defined an ODBC Data Source though the Pervasive ODBC Engine Interface and a connection in the DBC which pointed to it, not using a connection string.
>
>After upgrading DacEasy I find that it now accesses data via a service in the terminal that talks to an engine in the server which in turns acceses the files on disk. In the installation a Workgroup version of Pervasive gets installed in the server.
>
>The application needs to coexist with the new version of DacEasy. I see a couple of possibilities.
>
>1) Leave application the same and adapt at the environment level
>2) Adjust appliction to access data via the resident service
>
>So far I have tried to implement #1, running the data engine locally to access data in the server. Problem is that the engine I now have available to install in terminals is the workgroup engine, possibly different than the plain standalone engine, which I no longer have, and also that I have to attach the remote database to the local engine and run into a rights problem.
>
>For the second option I don't know how to connect to the service running at the terminal or how to talk directly to the engine running in the server.

If DacEasy has changed their data architecture, likely you are not the only person having issues like this :) First, I'd check DacEasy to see if they have a new or updated SDK or API specifications. The advantage of going to DacEasy is their information will be specific to their application.

If that fails, maybe you can determine the version of the engine(s) they are using, and then look for ODBC or OLEDB drivers at the Pervasive site. This would not have DacEasy-specific information, you'd be "rolling your own" data access. Depending on how/if security is implemented it may not even be possible to access DacEasy data directly with generic drivers.

Also, I think Doug Hennig has considerable experience with Pervasive.

http://connectionstrings.com/pervasive