Dan Waters
dwaters at usinternet.com
Tue Dec 11 11:23:34 CST 2007
I suspect that MS is doing this gradually. >From reading MS info on A2007, you cannot create a database in A2007 that uses ULS. You can convert a previous version database to A2007, and then A2007 will support ULS. But people can't, with only A2007, create a database which is password protected. For many or most companies that is a prerequisite for a 'critical' database. Last year I made a chart to help explain this. I think that MS saw the same 'red zone' that I see and wants to create a gap instead. That will separate casual users from people who are determined to be developers. And JC - notice that Classes are right up on top! http://www.promationsystems.com/PSI/Info/accessskillzones.htm Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka Sent: Tuesday, December 11, 2007 10:05 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access 2007 ULS (was: Access 2007 - Microsoft is justplain stupid.) But Access 2007 still let's you create databases in 2000 or 2002-3 formats, which can use ULS. So, they are just guaranteeing that if a developer wants to continue to use Access, w/ULS, that they aren't going to use the new format. On top of that, removing ULS is not going to prevent 'too many people' from creating personal/business databases that grow into critical databases....it is just going to ensure that if they do it with a 2007 format, that there will be little to no security in it. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Monday, December 10, 2007 7:48 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Access 2007 ULS (was: Access 2007 - Microsoft is justplain stupid.) I think what MS did with User Level Security in A2007 makes sense (I'm not saying I like it). What it does is continue to allow the use of Access for individual productivity, but prevented it from being used for shared secured databases except by people who had at least enough skill to make Access work with SQL Server. The business problem with Access has been that too many people got into trouble as they grew their database, and then IT departments began to hate it because they had to take over a very flawed, department critical, database with no budget and no time. Dan -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com