Douglas sorted me out on this one...but I see he only emailed me. I don't want to confuse anyone checking the archive, so I'm passing the thread back up. First Douglas' message to me and then my response:
The docs read per below Position of its first occurrence if the value is found; otherwise position where the value should be inserted That should do it? ---------- Forwarded message ---------- From: David Adams <[email protected]> Date: Sat, Jan 14, 2017 at 5:51 PM Subject: Re: Tip: Binary insertion code To: Douglas von Roeder <[email protected]> I see. Clearly, I'm always the last to know. But like they say, "Why reinvent the wheel when you can reinvent the whole car..." ;-) Doug, thanks for letting me know. As it stands the sample code is potentially still of some use to any of our friends using V14 R3 or earlier. For anyone in that camp, I ran my limited test cases through the 4D command it provides the same answers as my code. The 4D code is better because in a lot of ways, particularly that it tells you if the position indicates where the target value *is* or where it *should be.* Super handy. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
