don't use the sa account for a DSN. you're potentially giving someone access to your entire database server - not just that database, and with that, the potential to also affect your database filesystem.
create a user in the security tab of the db server - allocate it to a database and give it read priviledges. Now use this use user for your DSN. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: 25 February 2003 16:21 > To: [EMAIL PROTECTED] > Subject: [ cf-dev ] SQL 2K DSN > > > Woo Hoo > > Forget it I have just solved it at long last ...... > I went on the SQL server course last week and now understand the > permissions given to a database a little better. > I used the sa account and it actually worked ..... > > Woo Hoo - What a dumb ass I didn't try it in the first place.... > > Regards - Paul > > > > > ************************************************************* > This email and any files transmitted with it are confidential > and intended solely for the use of the individual or entity > to whom they are addressed. If you have received this email > in error please notify [EMAIL PROTECTED] > > The views expressed within this email are those of the > individual, and not necessarily those of the organisation > ************************************************************* > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
