Hello.
I use bussiness application which uses Pervasive v8.0 or 2000i through
Pervasive Client (which doesn't need ddf files). This application can
generate ddf files and I can access to its database through odbc. But I
have 1 problem. If i write other application which has access to db
through odbc I have to share ddf files and everyone can view/edit db
files. I know that I can put privaledges to db (passwd to whole db in
200i,v8.0 and provaledges to tables in v8.5) but the source application
can't support privaledges so I only can change perrmissions to ddf's. Is
there any trick to limit access only to ddf files (source application
doesn't need theese files)?

bye, Adam

You can put some limits on them.
You can remove the user rights to them. You will still need to have
the engine have OS level rights to the files. This varies by OS.
Windows: Whatever account the Pervasive services log on as by default
the built in System account will need to have rights to them. Nobody
else will.
Novell: No rights needed.
Linux: Again whatever account the Pervasive "services" log on as, by
default the 'psql' user.
But once the ODBC data source is defined any client can create an ODBC
connection to it unless SQL security is turned on.
At that point you may want to put restrictions on what tools the users
have on their computers.

Leonard

On Mon, 31 May 2004 09:03:39 +0200, "[BuKoX]" <bukox_WYTNIJ_ (AT) tlen (DOT) pl>
wrote:

Instead of messing with file security, I would simply enable SQL-level
security on the DDF's. This will not impact the application at all, and
will require anyone coming in from ODBC to log into the DDF's.
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: June, 2004: See our web site for details!


"[BuKoX]" wrote: