Atkins

Before you got to reply, I have found the problem.  Fortunately, I found an older refi file I had prepared which didn’t crash.  I had omitted to place text in the module variables, right at the end where there is a bright red ‘mark’ symbol!  Once I put some text there, it no longer crashes.  (In effect, it is a title within the reference.)

 

Suggestion for improvement: I suggest that allowing for no text in that module variable would be an improvement, as there is no diagnostic info given that text there is vital and otherwise the reference will crash as soon as you try to do a search.  An alert that this field is blank might be an alternative solution.

 

John

Thanks all.

This is very helpful.  

Katoog, thanks for the PDFs.  I think it will be just what I need so I can find out what I need to find out.  As they are PDFs, they will port easily to the iPad.

JPG, loading the font will help me with the PC version but I am not sure how it will help me with the version that I will convert to use on the more mobile iPad.  It isn't clear whether I can load ad-hoc fonts into the iOS environment.  I am not prepared to jail-break.

Patchworkid, I feel for your loss.  When "data disappears, even strong men cry", as I have heard it said.

That said, I am not launching (I think) into a detailed scholarly understanding of OT Hebrew.  Rather, I am seeking just that "little bit more" to help me to overcome the shortcomings of Strongs in my use of the Hebrew OT in parallel with the OT passages I am reading.  Strongs certainly gives a "word meaning sense" but lacks the information on the word in its local context (person, number, article, case, etc) that permits investigation of the meaning in context.  I read somewhere else that understanding the Hebrew mindset of the day is almost more important than an accurate understanding of of Hebrew itself.  Perhaps I need to delve there,  as well, in time to come.

Thanks again,
JEA