Re: RDS Security issues

David W. Fenton wrote:
Bob Alston <tulsaalstonsNOSPAM@xxxxxxx> wrote in
ByT2f.15172$fE5.10362@fed1read06:">news:ByT2f.15172$fE5.10362@fed1read06: 


lylefair wrote:

I've followed recent posts. You've posted a lot about DAPs and
your posts have shown that you know almost nothing about them,
databases, or programming in general.

If there is a Security Flaw, state cearly what it is.


Below are a few links referencing the issue with RDS.

http://groups.google.com/group/microsoft.public.access.dataaccess.p
ages/browse_thread/thread/e05a0cc9c3b8105c/5d5de6c5c59fa498?q=rds&r
num=9&hl=en

http://groups.google.com/group/microsoft.public.access.dataaccess.p
ages/browse_thread/thread/485fe41aba913404/b8620ef1a9afb8ba?q=rds&r
num=25&hl=en

http://groups.google.com/group/microsoft.public.access.dataaccess.p
ages/browse_thread/thread/e05a0cc9c3b8105c/5d5de6c5c59fa498?q=rds&r
num=9&hl=en 


Tjhis is a duplicate of the first thread.


http://www.carlprothman.net/Default.aspx?tabid=102


Lyle has clearly stated *in this thread* that his DAPs connect to
SQL Server, not to Jet back ends, so RDS is simply not involved.

So, in this context, you are wrong that there's an RDS security
vulnerability with DAPs that use SQL Server as the back end.

Actually, as I recall, Lyle responded to my new post/start of a new thread entitled "Wouldn't it be nice if the new version of Access..." It was I who retitled the discussion to "RDS Security issues", to better focus on the real issue I was mentioning.

Again, as you have clarified for me before, like it is not use of Access in a web application that uses a database in a MDB file, rather it is Jet, it is not DAP that in of themselves have a security flaw, rather it is the RDS capabilities which are required to use DAP with JET databases which are flawed. I again stand corrected of erring in syntax.

I don't mind people correcting me if I am wrong, but to go out on the attack just because you don't agree with someone is going far beyond correcting their misstatement.

Bob
.

Relevant Pages

  • Re: why>?
    ... On your desktop-- you'll be running SQL Server behind the scenes. ... it isn't risky to allow end users to create databases. ... it is no more risky than giving you the ability to create spreadsheets. ... I'm not saying that Oracle and IBM are going away. ...
    (microsoft.public.excel)
  • Re: Please answer my queries for fresh Installation
    ... Moving SQL Server Databases ... Using WITH MOVE in a Restore to a New Location with Detach/Attach ... Disaster Recovery Articles for SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Please answer my queries for fresh Installation
    ... You can restore MSDB as well as master. ... > SQL Server, It will create Master, MSDB databases. ...
    (microsoft.public.sqlserver.server)
  • Re: Moving SQL Server 2000 from NT4.0 to Windows 2003
    ... Detach your existing user databases, ... user databases (or RESTORE) to the new server. ... > Hey Steve, ... Windows 2003 will not allow SQL Server SP less than 3. ...
    (microsoft.public.sqlserver.server)
  • Re: The best elegant solution to override 65k rows limit in a sheet
    ... MDB is friggin dead.. ... SQL Server has taken over the world. ... than read-only access to central company databases. ... I learned to write queries in Access after an hours' ...
    (microsoft.public.excel)
Loading