Re: oledb


"Sergey Berezniker" <sergey@xxxxxxxxxxxx> wrote in message
news:O1RlVtWMJHA.3496@xxxxxxxxxxxxxxxxxxxxxxx
Paul Pedersen wrote:
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?





Hi Paul,

It'll do nothing to improve security. Anyway all the processing will be
done on workstation and it'll have to have access to shared data.

Thanks. Not being familiar with OleDB, I didn't know that.



.

Relevant Pages

  • Re: oledb
    ... OLE and OLEDB require access to the directories hosting the files, ... means anyone using the workstation can also do the same - therefore there is ... If you want security, ... current file server system? ...
    (microsoft.public.fox.programmer.exchange)
  • 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. ...
    (microsoft.public.fox.programmer.exchange)
  • oledb
    ... A couple questions re oledb: ... I have an application that uses FoxPro tables in a simple shared folder on a ... Will this do what I want, i.e., considerably improve security over the ... current file server system? ...
    (microsoft.public.fox.programmer.exchange)
  • ACLs
    ... I have a shared folder on my file server and I need to ... lock down security on it using the ACL's. ...
    (microsoft.public.win2000.security)
  • RE: FSMT - Default Share and Location
    ... "The File Server Migration Wizard eliminates this problem by using default ... target shared folder names that have the format Sharename_SourceServerName, ...
    (microsoft.public.windows.server.migration)