I'm a long-time user of Btrieve, but there's something I've never fully
understood. If this question is plainly answered in some documentation
somewhere, please point me in the right direction, and I'll gladly RTFM.

How does the Btrieve requester figure out what server to send its requests
to?

It seems that all the Btrieve client requires is a path. I would
speculate that the Btrieve client does something like take "Q:\DBDIR\",
ask Windows the server path for Q: (\\MYSERVER\APPS) and then uses that
information to determine where to send requests (MYSERVER Port 3351).

That seems like a very roundabout way to determine what server you should
send requests to. Is that the way it works?

Besides the client's Workstation engine, the Server Engine running local
to the DB files is the only engine you can use, correct?

-Adam

You have the basics of the resolution process already!

You can get a very good understanding of the FULL DETAIL of what happens two
ways.
1) EASY: Start the SmartScout program (SSCOUT32.EXE, shipped with all versions
but V8) and run a Communications Test to the server with the path of your
choice. You will see most of the work being done in the report it displays.
If you have V8, you need to run the Pervasive System Analyzer and run the comm
tests, sending the report to a log file and viewing the log file -- ugly, but
it gives you most of the same stuff.
2) HARD: PSQLV8 ships with the Debug Requesters. Check the documentation for
these to install them correctly and use the Function Executor (WBEXEC32) to
open a data file somewhere -- then look through the (very long) log file.

Hope this helps...
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: September 16-18: See our web site for details!


Adam Augusta wrote: