Our company uses Pervasive Sequel Server to run a product by Windowbook software. We have a another program TRACs that when we try and install using SB Client on the same PC's, it creates a conflict with the Pervasive. Any work arounds for this?

What kind of "conflict"?
WHat is TRACs? Does it use the Pervasive engine as well?

It's not the TRACS that's causing the problem, it's the SB Client its self.

The System Builder client uses v6.15 Btrieve (W32MDKE.EXE) during it's use. So if you have any P.SQL tray icons running (W3dbsmgr.exe) the SB Client will fail.

I would get w32mkde.exe running before you try the install using the SB Client, it would already be loaded and the install should complete.

It seems that both programs use a Pervasive engine and we cannot get the two of them to run on one PC. Windowbook, which uses Pervasive.SQL8 is installed and running on a PC, when IT tried to install SB Client, the Windowbooks stopped working.

I would suggest trying the following:
1. Uninstall WIndowbooks.
2. install SB Client.
3. Make sure it works.
4. Install Windowbooks.
5. Make sure it works.
6. Check SB CLient. Does it work? If not, what exact error message is being returned?

Windowbook was installed on a PC, TRACs and SBClient was installed and Windowbook stopped running. We worked with Windowbook to uninstall and reinstall the Windowbook software and Pervasive SQL8 and at the time of the reinstall Windowbook worked. The PC that this was done on does not normally run Windowbook but the Tracs and SB Client. I asked the user to open Windowbook and it is not working again, we get the following error. "File P:\\WB\PMW\data\terms could not be opened. Error: Not a Btrieve file (30). Press OK to end this application."

The error 30 is most likely caused by a mismatched engine. In this case, the SB Client is probably loading an older engine. THe old engine can't read newer Btrieve files. What happens if you stop the Tracs and SB Client before running Windowbook?

Not sure what you mean by stop, Tracs and SB Client are not opened on the PC when we try and launch the Windowbook software. Does that answer your question? I guess you can tell my now I am not a IT person.

By stop, I mean make sure that it's not running and the Pervasive engine it uses isn't running.
If it's stopped, you might still be picking up the old engine. WHen you run Windowbook and get the error, is W32MKDE.EXE loaded in memory (You can see this by looking at the Process tab in Task Manager)?