Full text search is a tool for indexing parsed strings/memos. It can return result sets or counts for various expressions including "word and word", "Word or word", "word not word","word or not word", "phrase", "phrase and word", "phrase and not word" ect.
these expressions can be evaluated in VFP now but are not optimized without either strenuous coding, or third party tools. Developer solutions are nowhere as efficient as low level functionality or as reliable. For instance this website uses PHDbase for searches. PHDbase is a full text search engine which is used with FP/VFP. There are many problems using some third party tools, and this one in particular has a unique set of problems which were discussed in excruciating detail over the past year on this website. Another full text engine is dtSearch. It loosely integrates with VFP and requires offline indexing. Full text search is a feature in SQL Server but this is a VFP forum not SQL Server.
>>what do you think of Full Text Search as a feature for VFP 8.0? The current 3rd party options are pretty lame. A roll you own solution can work in a fairly static, low volume environment but not in large scale computing. I have proposed this to the VFP wish list because I am faced with FTS on EVERY web project I undertake.
>>
>>What do you think?
>>
>>Glenn
>
>Sorry, Glenn, but I don't quite understand exactly it is that is needed. Can you elaborate a bit?
>
>JimN
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only