Hi.

I have three memo fields in a table that I use TEXTSEARCH to look for words.

These fields are set for Indexing in the Full Text Indexing Tab in dbsys.

When a user searches one of the fields in the application the appropriate records pop up as having the search word in them.  Just as it should.

If I add some more records via the application TEXTSEARCH does not seem to work (on the new records) until I use dbsys to reindex the table.

Is this how it is meant to work or should the indexes be maintained?

Thanks.

Robert

>If I add some more records via the application TEXTSEARCH does not seem to work (on the new records) until I use dbsys to reindex the table.
>
>Is this how it is meant to work or should the indexes be maintained?

My DBISAM apps that use FTI all maintain the indices when records are added. Since I switched to ElevateDB my DBISAM is 4.25 and back then there was no discrete option to reindex a table. How do you reindex the table?

Roy Lambert [Team Elevate]

Hi Roy.

I thought it was not right.

I have all the indexes set and they all seem to work fine except those with TEXTSEARCH.  

I close down all instances of the application and use dbsys to reindex.  I do this every month or so, generally when I get angry to not being able to find a record with a particular address (memo) that I know is there.

The table was set up using dbsys.

I've attached a reverse engineer of it in case there is something glaringly obvious.

Thanks.

Robert


The only thing that looks different to mine is that one of your memo fields is compressed. Another potential difference is that I have a custom full text index module. What's being stored in the memo fields - is it plain text or something else?

Roy Lambert

Roy.

The compressed memo contains job notes and I use a WPTools RichEdit for formatting these.  I think I've seen you on the forums for WPTools so you know what I mean.  It therefore stores the actual notes plus the display codes.  This field is not really the problem. I'd forgotten this is compressed.  Maybes I need to remove the compression.

The address memo is the one most frequently searched.  This is plain text.  We have 40+ jobs in per month and I may need to search for one from a few months back.  I remember the town it was in and so do a search.  It does not appear.  It will after I've reindexed using dbsys.

What is a custom full text index module?

Rob.

Robert

>The compressed memo contains job notes and I use a WPTools RichEdit for formatting these. I think I've seen you on the forums for WPTools so you know what I mean. It therefore stores the actual notes plus the display codes. This field is not really the problem. I'd forgotten this is compressed. Maybes I need to remove the compression.

I can't see compression being the problem.

>The address memo is the one most frequently searched. This is plain text. We have 40+ jobs in per month and I may need to search for one from a few months back. I remember the town it was in and so do a search. It does not appear. It will after I've reindexed using dbsys.

>What is a custom full text index module?

Its a piece of code that trips out all html formatting, makes sure that only words not containing numbers, longer than and shorter than a specified length are indexed.

Roy Lambert [Team Elevate]

Robert,

<< The address memo is the one most frequently searched.  This is plain
text.  We have 40+ jobs in per month and I may need to search for one from a
few months back.  I remember the town it was in and so do a search.  It does
not appear.  It will after I've reindexed using dbsys. >>

Can you send me a copy of the table files that exhibit this behavior ?  The
full-text indexing works transparently, and should always have up-to-date
indexes, so something is seriously wrong if you're not seeing the indexes
updated properly.

Is this a multi-user, file-sharing application ?   If so, are you using
large file support in some or all of the applications accessing the database
?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim.

I've eMailed the table to you.