You can limit an indexed or an unindexed search to a specific field. For example, you could search for apple pie w/6 blueberry jam limited to a "subject" field.
	You can also combine full-text and field searching: visual basic and (name contains (Smith or Jones)).
	Field searching supports the complete range of full-text search options (boolean, proximity, fuzzy, phonic, wildcard, stemming, etc.).
	For a list of fields defined in indexed documents, click the fields button in the dtSearch Desktop or Network search request dialog box.
	See Developer FAQs for information on indexing and searching SQL (and Oracle) databases.

On-The-Fly Fields

In addition to fields that are predefined in databases and documents, dtSearch also supports a number of "on the fly" field options.

	dtSearch can find an expression between a beginning field market and an end field marker that you name. For example, you could search your letters for: dear to sincerely contains aunt agnes.
	dtSearch automatically inserts its own automatic field markers at the beginning (xfirstword) and end (xlastword) of all documents. You could use these markers to limit a search to the beginning or the end of a document, as in: apple pie w/10 xfirstword.
	File segmentation rules can break up long text files into multiple subdocuments, effectively treating each multiple subdocument as a field.
	The dtSearch Engine provides a large number of options for adding fielded data while indexing. Click here for overview article, or see Developer FAQs for more information.

PDF Fields

	dtSearch supports the handful of pre-defined fields in a PDF file.
	For additional PDF field support, some third-party products, like DocuLex, offer a few dozen additional custom PDF fields. DocuLex case study

XML Fields

As with any other document or database containing fields, dtSearch can perform indexed and unindexed searches using the full range of dtSearch search features across an entire XML database, or limited to specific fields. For example, visual basic and (name contains (Smith or Jones)) works just as well on an XML database as an Access database, a Word document, an HTML document, a PDF document, etc.

Because of the special nature of hierarchical XML data, dtSearch also supports searches limited to precise combinations of fields and subfields. For example, in the Shakespeare XML database posted at here, you could search for:

• persona contains Henry
• scene/stagedir contains exeunt citizens
• scene/speech/line contains publius
• /play/title contains Henry the Fifth
• scene//line contains publius

The first example would look for any field entitled persona that contains Henry. The second search containing the / as a field separator would look for a field called stagedir containing exeunt citizens, with the stagedir field directly nested in a field called scene.

The third example would look for a triple-nested hierarchical scene/speech/line field sequence that contained publius. The forth example, starting with the /, would look for the play field at the top of the hierarchy, with a title field just beneath it containing Henry the Fifth.

The last example, with the //, would look for a field called line containing publius. In contrast to the other examples, which specify precise hierarchical sequences, in this last example, the line field could be anywhere from directly beneath the scene field, to nested at multiple levels of depth.

Finally, it is also possible with an XML database, as with any other fielded document or database, to combine full-text searching and nested field searching. For example, a combined full-text and fielded search over the Shakespeare XML database might be: (henry the fifth) and (scene/speech/line contains publius).

Click here to try the online XML Shakespeare search demo.

does instant thesaurus/concept, natural language, fuzzy, phonic, boolean, proximity, field, numeric range searches through gigabytes of Word, WordPerfect, database, XML, HTML, PDF, ZIP, Office XP files