Mary Chipman from Microsoft gave one the most complete yet compact answers on this topic yet.
...There are no plans for supporting designing SQL Server objects using Access ADPs either now or in the future. You can use Access to connect to a SQL Server 2005 database in 2000 compatibility mode, but there is no support for new 2005 functionality being planned. It is recommended that you use the client tools in SQL Server for creating new SQL Server objects. There is also support in Whidbey for creating SQL Server objects.
'nuff said!
Suppose you're writing a generic data access layer (DAL) that executed a command and cached the results some place. You want that DAL to be smart enough to either execute the code and cache the results or just pull the results from the cache if it can. What could you use for a key on the cached object?
You may say that all you need is the command text, but that ignores that different parameters might generate different result sets, so you need to consider those too. However, its hard to serialize all of that out into a single string as key, right?
Answer Here
Thanks to Andrew and Adam for getting me off my tukas about posting this.