Hi,

we have the following problem. On a Win2KServer (or Win2003Server) we have PSQL
8.x installed. Than we have a set of Btrive-files and a application, that
accesses that files via btrieve (not SQL/ODBC - just native Btrieve BTRCALL-API).

In this situation the clients must know the real networkpaths to that
btrieve-files. As far as we know: to update/insert records the client-user must
have write-rights on that btrieve-files.

Now the question: is it possible to restrict the write-rights to that files for
the usual client-users (on windows-level), but make pervasiveSQL-Server able to
update/insert nevertheless?

The PSQL-server-service on the Win2003server runs under higher rights than the
client-users.

In former Novell-versions this was possible!

Any hint will be wellcome.

Regards
M. Malarski

This is possible with all versions of Pervasive.SQL V8.5 and higher
(including v8.6, v8.7, v9.0, and v9.1).

What you want is the "Advanced Security" infromation -- for which you
should read the manual carefully (plan to have an hour of quiet time to
review the contents and concentrate on it), and then implement on a
test server first. It isn't very clear unless you understand the
database, but once implemented, you can lock out all user access from
the OS level (in fact, don't even need READ access to the database) and
still use the database from both Btrieve and SQL/ODBC.

The added security is WELL worth the time investment, but don't
shortchange the process -- plan to have lots of time to test before you
do this in a live environment...
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - July 19-22 ***
*** Chicago: Pervasive DataExchange Class - July 27-29 ***

nmm wrote: