>Ok, I can see your point.
>
>How then would you prevent someone from gaining access to a data access
>object?
>
>This DLL might extract pay scales, tax rate or invoice info. You dont want
>this data freely accessable to any developer.

Kevin,
If this is remote data and from the emphasis on security, I'm guessing it is, I would secure the data at database. You will need to do this if you want to keep developers from doing anything.

Developers don't have to go through the objects. They can connect to your database and use SQLExec() to bring down pay rate data if they want. Securing the Data object doesn't secure the data.

FWIW, this is different than places I have worked. Developers are SuperUsers or Administrators for systems. As such, they are given complete access to data to troubleshoot any problem that may arise. If they can't get to the data, they may not be able to correct a problem. Just my $0.02.

Regards.