dreamweaver mx/cfmx 6.1 rds - OT

2004-04-07 Thread Whittingham, P
Hi All, I am using Dreamweaver mx and CFMX 6.1 professional and would like to use RDS support. This would only be used on our dev boxes. We have lots of curators and databases. We would like to sandbox these databases so that a given curator can only see his/her tables/views in all of their

Re: dreamweaver mx/cfmx 6.1 rds - OT

2004-04-07 Thread Adrocknaphobia
what db are you using? you can set granular security roles with most enterprise dbs. -Adam -Original Message- From: Whittingham, P [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 7, 2004 01:14 PM To: 'CF-Talk' Subject: dreamweaver mx/cfmx 6.1 rds - OT Hi All, I am using

RE: dreamweaver mx/cfmx 6.1 rds - OT

2004-04-07 Thread Whittingham, P
PROTECTED] Sent: Wednesday, April 07, 2004 9:22 AM To: CF-Talk Subject: Re: dreamweaver mx/cfmx 6.1 rds - OT what db are you using? you can set granular security roles with most enterprise dbs. -Adam -Original Message- From: Whittingham, P [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 7

RE: dreamweaver mx/cfmx 6.1 rds - OT

2004-04-07 Thread Dave Watts
I am using Dreamweaver mx and CFMX 6.1 professional and would like to use RDS support. This would only be used on our dev boxes. We have lots of curators and databases. We would like to sandbox these databases so that a given curator can only see his/her tables/views in all of their

RE: dreamweaver mx/cfmx 6.1 rds - OT

2004-04-07 Thread Whittingham, P
: dreamweaver mx/cfmx 6.1 rds - OT I am using Dreamweaver mx and CFMX 6.1 professional and would like to use RDS support. This would only be used on our dev boxes. We have lots of curators and databases. We would like to sandbox these databases so that a given curator can only see his/her tables

RE: dreamweaver mx/cfmx 6.1 rds - OT

2004-04-07 Thread Dave Watts
Thanks. So, if we did get Enterprise, what would be necessary. Would I use the db security (Oracle/SQL Server/Access) or something else? At that point, you wouldn't need to rely on database security, in the sense that you wouldn't have to use USERNAME and PASSWORD attributes within CFQUERY.