You don't really have to forget about Jet. Actually the MS-Access/Jet combination makes it easy to "explore" data.
The thing that you have to keep in mind is that Jet existed long before there were any effective SQL standards. Because of that, the guys that designed it borrowed a lot from the file oriented databases and tools of the day. Those techniques are really convenient for the "data monger" that likes to roll up their sleeves and get into their data, but they really don't scale up very well.
SQL Server was designed to implement the SQL-92 standards, and it goes pretty much "by the book". Because of that, it scales very nicely... Actually FAR beyond what most people expect of it.
You can blend the two reasonably well, but when you do you are limited by the "smallest pipe" in the process, which is almost always the MS-Access/Jet combination. I'm not saying that there is anything inherantly wrong with the tools, I actually love them for what they do well.
In the same sense that I don't do spreadsheets using MS-Word, even though you can do some really creative things with tables, I also don't use MS-Access/Jet to manage OLTP type databases. I do have cases where I use DTS to build rollup/extract files that my users love to play in, but they don't get to play in the "big pool" without a very watchful "life-guard" to limit the damage they can do to themselves and others.
Thank you Pat that explains alot, good grief you've been programming in sql for a long time I assume. I wish I had your knowledge, gonna take me awhile to get to your level...a looong while. But I really like working with sql, I'll get there eventually