One can query indexing service directly in Windows XP Pro. (Heme too, I
THINK but am not sure).
My Computer->Right Click->Manage
Services and Applications->Indexing Service
(If it's not running then it must be started of course and if it's never
run it will need considerable time to build a catalog)
Click on a catalog, the default catalogs I have seen have been named
"system"
Click on Query the Catalog
Type in your query
Help->Help Topic->Index->queries: gives one an extensive list of query
formats.
That's it.
one can get such exotic info as music genre and image dimensions
---
---
or one can write an app using ado to do this
---
I gave up running anti-virus software some months ago after having done
so for several years. I don't remember any of the problems outlined in
this article having occurred.
---
So what are desktops search engines for? ... beats me.
----
my use of is has been in ASP-ADO-Internet applications
MGFoster wrote:[color=blue]
> Lyle Fairfield wrote:
>[color=green]
>> MLH <CRCI@NorthState.net> wrote in
>> news:d7nk61h0lrl3dru7137jvqjf5naq23i2tt@
>> 4ax.com:
>>
>>[color=darkred]
>>> I have a RDBMS app consisting of 3 primary mdb's...
>>> 1) a front-end with a few STATIC tables and the other menagerie of
>>> objects
>>> 2) a back-end with most of my DYNAMIC tables. I'll call it my main
>>> backend.
>>> 3) another back-end = zip.mdb with about 43000 zips/cities/states
>>>
>>> The app has been operating stably (is that a word?) for some years.
>>> No probs. The main backend is 63.3 megs now and contains tens of
>>> thousands of letters - legal documents sent to attys, litigants, gvt,
>>> judicial bodies - you name it. Pure text in a memo field - the entire
>>> letter from dear mr jones to yours truly, john doe.
>>>
>>> Probably upwards of 40 megs of the main backend's size is due
>>> to the contents of this single memo field. Is there any reason on this
>>> earth for me to consider breaking out the contents of this memo field
>>> by putting into a linked table in what would then be a THIRD backend
>>> database? Any reason at all? Mind you, I would have no other
>>> objectives other than efficiency in mind for doing this. Rarely (if
>>> ever) is the field's contents searched in ANY fashion. If I want to
>>> find a particular letter, there are PLENTY of other fields to query
>>> it out precisely. And the last thing worthy of mention, I think, is
>>> the fact that these letters are being maintained for legal
>>> responsibility only. It is damned near certain that only 1 out of
>>> a thousand will ever need to be reproduced again for any reason.
>>> If I knew which one, I would HAPPILY delete the other 999 if you
>>> know what I mean. The other fields in the correspondence table
>>> are far more valuable, in my opinion, to my overall needs as they
>>> serve as a record of my having sent the letter, to whom, when, where,
>>> etc... and even are topic-categorized to give one a pretty
>>> good idea as to what the letter was concerning without even reading
>>> it. So, its like separating useless (well not useless) from more
>>> useful things (IE, the wheat from the chaf). What I'm really trying to
>>> say here, dammit, is that if I could really afford a data loss
>>> somewhere - it could be one of these confounded letters that
>>> are eating up my disk.
>>>
>>> Bottom line question for the gurus is: Do I really need to serious
>>> consider carving out the huge block of memo data and putting
>>> into its own database?
>>>
>>> Thank-you for your patience in reading this rather lengthy post.[/color]
>>
>>
>>
>> Keeping tack of documents may be done vwry efficiently with Microsoft
>> Indexing Service and the ADO Microsoft Indexing Service Provider. With
>> it we keep track of what is stored in files and a file is similar to a
>> memo field. The file can be a Word doc, or whatever.
>>
>> From ADO help:
>> "The Microsoft OLE DB Provider for Microsoft Indexing Service provides
>> programmatic read-only access to file system and Web data indexed by
>> Microsoft Indexing Service. ADO applications can issue SQL queries to
>> retrieve content and file property information."
>>
>> Although it may take a little time to familiarize oneself with this
>> technology, it is so fast and so powerful that it's likely to be worth
>> it.
>>
>> My experience with it has involved large handbooks of many documents.
>> A field nurse has been able to look up blood near transfusion to find
>> all the relevant documents dealing with thsese realted topics.
>> A school principal has been able to look up bomb threat.
>> If indexing service is running then these lookups are seemingly
>> instantaneous, even if there are many thousands of documents.
>>[/color]
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Lyle,
> That's another good reason to use ADO ;-). After reading your post I
> searched thru MS's website for info on Index Server & found the
> following troubling quote:
>
> "Do not run antivirus programs while Index Server is running, or when
> you back up the Index Server catalog."
>
http://support.microsoft.com/kb/247093
>
> I'd be loath to run my PC w/o my antivirus running ALL the time (since
> I'm usually connected to the Internet - and just on general principles).
>
> There also seems to be some confusion (at least to me) about what the
> service is meant for. There are a lot of articles on using the IS w/
> IIS and virtual directories, and only a few (that I could find) about
> using the IS on local PCs. I'm assuming the IS can be used in both
> situations. How did you use IS (and how did you get such cool jobs? :
> )).
>
> Rgds,[/color]
--
--
Lyle
"The aim of those who try to control thought is always the same. They
find one single explanation of the world, one system of thought and
action that will (they believe) cover everything; and then they try to
impose that on all thinking people."
- Gilbert Highet
