David McAfee
DMcAfee at haascnc.com
Thu Oct 30 15:58:59 CST 2003
I totally agree with Arthur on this. Create individual users (can even use fosUser() function from Shamil's site to get the NT login name of the user) and assign roles to that user. As far as local files/tables go, Martin I think the temp db is the easiest thing to use. Small bit of code, and now your are dealing with the data using ADO or DAO. Stuff that he is more likely to already be using. Now I know XML gives better cross platform sharing capability, but for ease of use, I have to say talking to another Access DB is much simpler. D -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Arthur Fuller Sent: Thursday, October 30, 2003 4:25 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer]Linking to Local Table Not out of the blue at all, Martin -- IMO the preferred solution :-) That said, one cannot help but wonder why all users share the login, particularly when there are integrated security and roles available for use. With a single or even a few shared logins, all hope of accurate audit-trails is lost. Arthur -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Martin Reid Sent: Wednesday, October 29, 2003 10:41 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer]Linking to Local Table Bit out of the blue this but what about a local XML file. Martin --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.530 / Virus Database: 325 - Release Date: 10/22/2003 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com