[AccessD] Dialog Box for Creating .txt tables

...I've stayed away from the access uls mostly because its illusionary and 
prone to many problems ...there are so many hacks freely available that its 
useless ...I use a be usys table to manage security rights, turn off the 
system tables visibility at startup, and put the be on a hidden server share 
...its not perfect but so far so good ...any better ideas are welcome.

...I work for small companies where every user has to be able to 
update/enter data, so restricting some to read only isn't really feasible no 
matter how much I'd love to do it.

...in fact, I implemented my current (very basic) audit change logs to be 
able to show exactly who did what, when, and where in key tables ...amazing 
how fast the data entry errors disappear when the owner suddenly has the 
ability to nail the guilty party with proof positive.

William

--------------------------------------------------
From: "Drew Wutka" <DWUTKA at marlow.com>
Sent: Thursday, March 19, 2009 10:19 AM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Dialog Box for Creating .txt tables

> Actually, if you use Access User Level security (another reason to stay
> away from Access 2007), you can remove change rights for the Admin
> account.  So users using your application log in with an account that
> has rights to modify data, but if they want to query the data, the get
> read only capability.
>
> I've done that with a few databases around here, where only certain
> people should be able to change the data, and everyone should be able to
> view it.  Those few people get a login, the rest just open the mdb.
>
> Drew
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hewson, Jim
> Sent: Thursday, March 19, 2009 9:13 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Dialog Box for Creating .txt tables
>
> William, your statement below has me intrigued.
> I am working on a proposal for group of researchers that want to be able
> to query the data from a questionnaire that students fill out.
> You stated below "you have to provide a custom query engine for the
> users."
> How do you do that?
> Thanks,
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William
> Hindman
> Sent: Thursday, March 19, 2009 2:12 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Dialog Box for Creating .txt tables
>
> ...an mde on a full access install only protects your code, not your
> data
> ...a power user wannabe can use a full install to run queries against
> the be
> data that can do immense and sometimes uncorrectable damage simply
> because
> they only "thimk" they know what they are doing ...I've walked away from
>
> jobs over that issue ...I grant that's a luxury others may not have.
>
> ...on the other side, that means you have to provide a custom query
> engine
> for the users to have limited access to find the data they need without
> my
> helping hand ...find the data, not modify it in any way that I don't
> control.
>
> William
> The information contained in this transmission is intended only for the 
> person or entity to which it is addressed and may contain II-VI 
> Proprietary and/or II-VI Business Sensitive material. If you are not the 
> intended recipient, please contact the sender immediately and destroy the 
> material in its entirety, whether electronic or hard copy. You are 
> notified that any review, retransmission, copying, disclosure, 
> dissemination, or other use of, or taking of any action in reliance upon 
> this information by persons or entities other than the intended recipient 
> is prohibited.
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>