Re: THANKS! -> Re: For "TC" - Request for Clarification on a Comment You Made

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

> Yes, I'm not sure if I understood the original question,

If you mean my original question here, it was that MS-Access security
limitations seem to break (even SQL Server depending on circumstances). (David
described some perfectly "normal" circumstances)

If I'm confused, it is only because there are so many different circumstances.
Users who aren't supposed to have access at all, sneaky users who are supposed
to have only "limited access". If I have a problem, it is because my damn boat
"leaks" as well <vbg> (I do have a boat and it leaks)

I think it is specious to suggest "SQL Server" is of itself more secure, if
the front-end is "leaky" (even as David pointed out Excel/ODBC). Therefore, it
seems a requirement to hide how the Front-end works.

MS-Access has two obvious security limitations:
-ULS can be broken. Not technically by an "average idiot" though certainly by
an internet search. Even if (MS) 10-timed the technicals, if someone breaks it
and posts on the internet, well, that's how I know about quarks and
galaxies...
-MDE can be broken. Though it is said only forms and reports (so far), in fact
it is more than that. At least public functions are exposed in some
"break-ins". So unless one writes one's app with that in mind (simple example,
function called "decode") then "Houston has a problem". I liked to set SQL
Recordsource in form startup code, rather than in a Query----WHAT A WASTE OF
TIME.

The most secure FE might be a full exe, such as writing in C++. I know C++ (I
write DLL extensions to MS-Access in it), but it takes me (speaking only for
myself) 20x longer to write stuff in C++. Worse, DLL extensions in C++ sill
need to have the callables defined in the VBA, therefore, anyone can call the
individual routines.

Yup. Security makes my head hurt, that's for sure!!
Chris


.

Relevant Pages

  • Re: THANKS! -> Re: For "TC" - Request for Clarification on a Comment You Made
    ... Well thank you, David Epsom. ... At one end, a "corporate environment" no doubt has other security measures, ... SQL Server cannot apply in my case above. ... I can't conceive of a user having to logon twice (once to MS-Access ...
    (microsoft.public.access.security)
  • Re: Conversion of an MS Access application
    ... both the data and the program design. ... You ask any developer of MOST platforms, ... the idea of using database security DOES NOT apply to ... ms-access does include a database, ...
    (comp.databases.ms-access)
  • Re: Opening up a word document and then running a mail merge
    ... ms-access does word use? ... If you move the location for the mdb file, then again the connection to ... if you have security setup, then again, the word ...
    (microsoft.public.access.forms)
  • Re: Password limitations
    ... Now...how to prove that to the external auditors!! ... > Therefore you may want to check the other supporting security measures ... >>> limitations and cannot be changed. ... >> concerned about protecting the data from outsiders then place the file in a ...
    (microsoft.public.access.security)
  • Re: Password limitations
    ... I provided an audit a while ago ... Therefore you may want to check the other supporting security measures ... >> limitations and cannot be changed. ... > concerned about protecting the data from outsiders then place the file in a ...
    (microsoft.public.access.security)