Re: oledb
- From: "Zootal" <msnews@xxxxxxxxxxxxxxxxx>
- Date: Sat, 18 Oct 2008 15:14:28 -0700
OLE and OLEDB require access to the directories hosting the files, which
means anyone using the workstation can also do the same - therefore there is
no security.
If you want security, don't use VFP native tables. VFP tables <> security.
MySql and other back end databases will probably meet your needs quite
nicely.
There are ways to put the tables on a secure machine and have some
application handle the i/o, but that is way more trouble then it's worth.
I've seen it done - you will reinvent the wheel ten times over before you
get it working. Much easier to just switch to some back end database.
You can use an encryption product to encrypt your data. That won't stop
people from accessing the files themselves, but it will prevent them from
seeing what is in the data. It's a bit of work, but it's been done. Just be
very carefull - I once saw Cryptor permanently encrypt the tables. The user
didn't have a backup, and they lost many months of data because of that.
"Paul Pedersen" <nospam@xxxxxxx> wrote in message
news:%23p8jncWMJHA.5844@xxxxxxxxxxxxxxxxxxxxxxx
A couple questions re oledb:
I have an application that uses FoxPro tables in a simple shared folder on
a file server. In order to improve security, I'm considering putting the
data on a Windows Server 2003 machine and accessing it via OleDB (as a
simpler alternative to moving the data to SQL Server).
(The workstations are not in a domain.)
1. Will this do what I want, i.e., considerably improve security over the
current file server system?
2. Believe it or not, I've never used OleDB. ODBC yes, but not OleDB. Can
someone point me to a tutorial?
.
- Follow-Ups:
- Re: oledb
- From: Paul Pedersen
- Re: oledb
- References:
- oledb
- From: Paul Pedersen
- oledb
- Prev by Date: Re: GDI+ security update
- Next by Date: Re: oledb
- Previous by thread: Re: oledb
- Next by thread: Re: oledb
- Index(es):
Relevant Pages
|
