[AccessD] Secured vs. Unsecured FEs

I work for a company where we outsource for other companies.  So they do own
the code.

We have something like the BEU in this one system where we supply a template
and the system adds new fields to the ends of records based upon the fields
in the template.  I spent hours tracking down a problem where the user
inserted fields in the middle of the record!  This caused only partial
updating of the new fields for the record.

We now have limited security on the MDE FE and the BE is pw protected.  We
also set the FE up so that users with the correct pw can access the linked
tables.  This pw changes with each release.  I know, I know, kind of slack
security, but we had to fight to get this far.  LOL.

Bobby

>  -----Original Message-----
> From: 	accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]  On Behalf Of Andy Lacey
> Sent:	Thursday, April 17, 2003 3:00 AM
> To:	accessd at databaseadvisors.com
> Subject:	RE: [AccessD] Secured vs. Unsecured FEs
> 
> My 2c
> I have never used an MDE and I have never had a user curious enough (for
> curious read stupid) to tamper with an FE. And that's a LOT of users at a
> lot of compnaies over the years. I must live a charmed life. I wouldn't
> hesitate to go the MDE route if I had to, but I never have.
> 
> (Just hadn't seen any posts on this side of the debate and couldn't stand
> the idea of the list being unanimous on any subject ;-) )
> 
> Andy Lacey
> <http://www.minstersystems.co.uk>
> 
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 2700 bytes
Desc: not available
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030417/9c30af21/attachment-0001.bin>