DTSearch and Long File names

We have built some bespoke apps on DTSearch, and its a smooth engine, but there are a couple of bugbears that we have had to work around.

These are not DTSearch problems, but just data problems.

 1. Long filenames.  We often move the data from a disc to a SAN, under some extra subfolders. This pushes the path length above the maximum. Windows then struggles to recognise these files and DTSearch can’t see them either. Therefore we move them to a higher level. I wondered if there is any application out there that can access and index files that are longer than the maximum length. I know there is a Linux version of DTSearch… does this help?

 2. Data files.
DTSearch indexes the records in MDBs, CSVs etc as individual documents. We now how to stop this, but I wondered what the purpose of this functionality was?

3. Zip files.

On a large data set, there is nothing worse than having to unzip everything first. However, it would be nice if there was a feature to stop DTSearch indexing the files within a zip file as separate entities. Does anyone know how to do this?

4. MSG Files

When extracting resulting files from DT Search, with HTML MSGs it has the annoying habit of exporting as a folder with constituant parts. I don’t know the solution for this problem. We want it to extract the original file! Help!

Martin.

2 Responses to “DTSearch and Long File names”

  1. Peter Says:

    I’ve been using the following library that resolves the long filename & path issue. It is not free, but comes with samples and working code. It saved so much of my time!

    http://www.abtollc.com/products.aspx

    There is no need to rename files or move to upper level, it just allows to work with files keeping their real long paths, thats all.

    Peter

  2. Albina-eh Says:

    ðóññêîå ïîðíî áåñïëàòíî äåòñêîå ïîðíîâèäåî ñêà÷àòü áåñïëàòíî ðóññêîå ïîðíî ñ ó÷èòåëüíèöåé ïîðíî ðóññêèõ ãîëûõ æåíùèí êðóòîå ïîðíî â äîìå 2

Leave a Reply