DB> I recently saw our new database wizard do some things that
DB> "aren't possible".  One of them involved getting to a second
DB> domain with out a trust relationship or a user account.  It
DB> is a special case, however, and he is an MCSE who happens to
DB> prefer database work to network admin. 
DB> If the user has backup rights to an Access or SQL database
DB> on one domain on a network, they can get to that domain from
DB> from a different domain from inside another Access or SQL
DB> database that they have backup rights to.
DB> If he can get to a command prompt on one domain, all
DB> resources on the network are fair game for him too.  Perhaps
DB> it doesn't count because he does need some subset of an
DB> admin account, but then there is "Get Admin" that a lot of
DB> administrators have not locked out of their networks. 
Interesting. WHen I first read this, I thought the account he had was on the 
SQL server where the DB was located. In which case, he would have an account 
on the server and could get to a command prompt. But it appears the account 
is not on the server, but within SQL.  Now how you can do this within Access 
is beyond me. Access is a file database, unlike SQL server which has 
processes running on the server of interest.
Frank  PE, CNE, MCSE, MCP+I, MCP
 framsey@goodyear.com, frank.ramsey@fallsbbs.com
---
---------------