I wanted to review past posts for protecting your distributed EXEs. I recall I asked about this a couple years ago. I found this in my 'armadillo' search: https://leafe.com/archives/msg/506233
However, when clicking the "View entire thread" (https://leafe.com/archives/full_thread/506233), the site then failed and just said "No results were found. Please try again."
(Flashing the big "E" in the sky for Ed Leafe to come save the day with the List management!!!!)
I actually did a search - for subject phrase of "PROTECTING YOUR DISTRIBUTED CODE" - and it seemed to bring up everything. I know the link you mentioned to "View entire thread"- but, the other worked - as a work-around...
-K-
On 11/27/2018 4:59 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
I wanted to review past posts for protecting your distributed EXEs. I recall I asked about this a couple years ago. I found this in my 'armadillo' search: https://leafe.com/archives/msg/506233
However, when clicking the "View entire thread" (https://leafe.com/archives/full_thread/506233), the site then failed and just said "No results were found. Please try again."
(Flashing the big "E" in the sky for Ed Leafe to come save the day with the List management!!!!)
[excessive quoting removed by server]
On Nov 27, 2018, at 6:59 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
However, when clicking the "View entire thread" (https://leafe.com/archives/full_thread/506233), the site then failed and just said "No results were found. Please try again."
Since there really isn't a guaranteed way of tracing a thread, since In-Reply-To: headers are notoriously unreliable, the "View Entire Thread" relies on parsing the subject of the current email, and finding others that match. It's a hack that works most of the time, but obviously not in this case.
Kurt's solution (doing a new search by subject) is the preferred method in these cases.
-- Ed Leafe
Look at that! Glad I could be of some limited use here - even though I'm no longer working in Fox - at least not right now...
-K-
On 11/27/2018 6:41 PM, Ed Leafe wrote:
On Nov 27, 2018, at 6:59 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
However, when clicking the "View entire thread" (https://leafe.com/archives/full_thread/506233), the site then failed and just said "No results were found. Please try again."
Since there really isn't a guaranteed way of tracing a thread, since In-Reply-To: headers are notoriously unreliable, the "View Entire Thread" relies on parsing the subject of the current email, and finding others that match. It's a hack that works most of the time, but obviously not in this case.
Kurt's solution (doing a new search by subject) is the preferred method in these cases.
-- Ed Leafe
[excessive quoting removed by server]
On Nov 28, 2018, at 9:43 AM, Kurt @ Gmail kurthwendt@gmail.com wrote:
Look at that! Glad I could be of some limited use here - even though I'm no longer working in Fox - at least not right now...
Heh, I haven’t had a copy of Fox for over a decade. So don’t feel bad. ;-)
-- Ed Leafe
Yeah Ed - I know. I've heard you mention that a couple times. So, I guess I'm in the same club now. Previously working w/Fox - yet no more - but, still hanging with the Gang!
-K-
On 11/28/2018 8:05 AM, Ed Leafe wrote:
On Nov 28, 2018, at 9:43 AM, Kurt @ Gmail kurthwendt@gmail.com wrote:
Look at that! Glad I could be of some limited use here - even though I'm no longer working in Fox - at least not right now...
Heh, I haven’t had a copy of Fox for over a decade. So don’t feel bad. ;-)
-- Ed Leafe
[excessive quoting removed by server]
On Nov 27, 2018, at 6:59 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
However, when clicking the "View entire thread" (https://leafe.com/archives/full_thread/506233), the site then failed and just said "No results were found. Please try again."
(Flashing the big "E" in the sky for Ed Leafe to come save the day with the List management!!!!)
I had a little time to dig into just what was causing this to fail, and noticed that all the replies somehow had newlines in the middle of the subject, which caused them to not match the original subject. I then found that there were nearly 6,800 such “broken” subjects in the database. I cleaned them up, and your link above should now work just fine.
-- Ed Leafe
-
Ed Leafe -
Kurt ＠ Gmail -
mbsoftwaresolutions＠mbsoftwaresolutions.com