How to fix this: VisualFilterSyncItem error: ClientError (Startup)

Hi Leon

Deon Holtzhausen said:

I found VisualFilter.db & VisualFilter.db-journal which I renamed by adding OLD in the file name. I started up Logos which built new files and there is no sync error any more.

That is really good news.

Deon Holtzhausen said:

Off-topic: What do you think is the best way to learn Logos. I come with Logos since Libronix but have only done VERY basic searches. Last year I bought a very good range of video tutorials from www.LearnLogos.com which is based on Logos 7.

There are some series of training videos available on the Logos website that take you through a study process. 

• https://support.logos.com/hc/en-us/articles/360017433892-Logos-8-Bible-Study-Series
• https://support.logos.com/hc/en-us/articles/360017433952-Logos-8-Sermon-and-Bible-Study-Prep-Series
• https://support.logos.com/hc/en-us/articles/360018345231-Logos-8-Academic-and-Theologian-Study-Series

They are geared around working through a particular study process and applying Logos tools in the appropriate places. You might find them useful.

Deon Holtzhausen said:

Like now ... I want to find all the places in the Bible where God, not Jesus, says: "I am ..." where the dots must be words like good, love and so on.

For me - it often starts with right-clicking something and seeing what follows!

So taking your example above - the first thing is to find words spoken by God. To work out how to do that I would go to a verse where God is speaking - such as Genesis 1:6 - and right click on one of the words he says. Then select the "Speaker" item on the left and run a Bible search

giving

so now I have all the places in the Bible where God is tagged as speaking.

Now I need to know that to find particular words within that I use the WITHIN operator

This gives 155 results which you might choose to work through and see which meet your criteria

Or you can add in the words you are interested in - such as "love"

Note that the "I am" BEFORE love is enclosed in brackets to indicate that the whole construct needs to be present in the words of God

The BEFORE operator says that the words "i am" need to come before "love" somewhere in the verse. Interestingly there is just one result and I don't think it qualifies for what you are looking for.

To force the search to only find occurrences where the descriptive word follows immediately on from "i am" you can use "BEFORE 1 WORDS"

As expected from above, this results in no hits

To specify different words that are being spoken after "I am" you enclose those terms in brackets and separate with a comma (just using the word "angry" to demonstrate!)

So your actual search string ends up as something like:

("i am" BEFORE 1 WORDS (love, good, kind) ) WITHIN {Speaker <Person God>}

with no results!

So it is important to know a few of the search rules, to know how the key operators work and then - often - you can build the search from there.

Hope this helps a little.

Deon Holtzhausen said:

("i am") <Root = lbs/he/טוֹב:1> NEAR {Speaker <Person God>} : This did return a search result, BUT, this one didn't, and the only difference is the extra brackets on the left of NEAR: (("i am") <Root = lbs/he/טוֹב:1>) NEAR {Speaker <Person God>}

1. If looking for words spoken by a person, then the words are WITHIN the text of {Speaker <Person God>}

2. "i am" doesn't need parentheses (...), as the words are already associated by the quote marks "..."

3. In a complex search, or one that involves different types of operators (like yours), use explicit AND OR

• "i am" <Root = lbs/he/טוֹב:1> is simple enough to work without AND, but your search is complicated by the NEAR (or WITHIN) term
• "i am" AND <Root = lbs/he/טוֹב:1> WITHIN {Speaker <Person God>}  will work because of precedence of AND, but
• ("i am" AND <Root = lbs/he/טוֹב:1>) WITHIN {Speaker <Person God>} forces evaluation within parentheses (...) to be first

I appreciate that "i am"  <Root = lbs/he/טוֹב:1> WITHIN {Speaker <Person God>} works, whilst ("i am"  <Root = lbs/he/טוֹב:1>) WITHIN {Speaker <Person God>} did not work, but it only illustrates the reason for the explicit AND in complex searches!