Thanks Erik

Those are all good hints that I will use.

I have found that "Search" at least gives a hint of the context because the 'source' appears in the listbox. Sure would be nice to have something similar for the Index, even if it involved moving the mouse over it to get the information.

Cheers,

JimN

>>This has been on my mind since I received and used my first issue, but it has come to the fore now that I have bought a machine with Win2K installed.
>>
>>I generally find that using the INDEX option (would seem to) serve me best. BUT. . .when I use it the titles displayed appear relevant until I access them. Then I find that they are related specifically to things like MSOffice or SQL Server or ACCESS - usually anything except what I am looking for.
>>
>
>When I am looking to learn about a general subject, I search on that subject in the index, click on one topis, and then click "locate" to find where that topic is in the contents. I then use the contents to navigate to the specific subjects that I want to look at. I might go to the top level of the specific subject I was looking at and add a bookmark. (too bad we don't have a way to preserve bookmarks from version to version of msdn).
>
>When I am looking for an explanation of a specific subject or feature, I use the Index. When I need to see a sample of how to use the feature or function, or want to see if there are any KB articles, I use the search. For example, to see if something I am looking at is a documented bug, I'll search on "myproblem BUG", and this usually surfaces the KB article. You can do something similar using "myproblem PRB" and "myproblem HOWTO" to get those specific types of KB articles.