Re: oledb


"Zootal" <msnews@xxxxxxxxxxxxxxxxx> wrote in message
news:ezkeG7WMJHA.2348@xxxxxxxxxxxxxxxxxxxxxxx
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.

It sounds then like there isn't much difference between ODBC and OleDB. I
was hoping that the server could make an OleDB source that would require a
password, while keeping the tables in a non-shared folder. I guess no such
luck then.



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.

I thought I might have to go that way. Would you recommend SQL Express or
MySQL?



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.

Thanks for the warning.



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.

That would be the easiest solution for me, and the security would be good
enough. But some of the workstations are running Vista, and the last I
heard, Cryptor does not work on Vista. Do you have new information? Or can
you suggest another product?



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.

Ouch! That would be very annoying to say the least. Daily backups then.




"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?








.

Relevant Pages

  • Re: SBS 2003 / Software Firewall?
    ... The server is protected in Single NIC installs. ... And workstations are where your security problems are. ... to protect it from an internal LAN attack. ...
    (microsoft.public.windows.server.sbs)
  • Re: Thin-clients: THE Solution to the Security problem
    ... workstations -> get rid of workstations. ... Most real-life security issues fall outside the scope of this ... Thin clients will give little or no increased security ... server room, DDoS, and so on. ...
    (Security-Basics)
  • Re: oledb
    ... inherent limitation of OLEDB! ... limits security. ... A product like Sybase's Advantage Database Server might give you what you ... native access while systematically converting to client server. ...
    (microsoft.public.fox.programmer.exchange)
  • Questions Re: users/groups, security and GPOs
    ... With my limited server OS knowledge, I'm struggling to get my head ... The current workstations are "survey1" through to ... The survey workstations frequently require access to each ... the server (rubbish security!). ...
    (microsoft.public.windows.server.sbs)
  • Need Security Guidance
    ... (Windows2000 Server) ... morning and establish a 56k connection to the ISP, ... PCFlank test reports security problems at the IP address related to ... but does not seem to see the workstations or file ...
    (comp.security.firewalls)
Loading