[quote author=SpencerWulwick  link=1133387185/0#11 date=1133400014]Now I am even confusing myself.

Marc -  I [b]know[/b] that recently I had tried searching for // and it would not work unless I typed ..\/\/..

YET, I just tried it using ..//.. and it worked just fine.  Is it possible you "fixed" (or changed) something in the most recent release of verion 1.1.3 ?  [color=Red]Would still like feedback on this point.  Thanks![/color][/quote]


Spencer,

Nothing was changed in 1.1.3 in regards to searching for '//' in an element. I just tried it here in 1.1.2 and you can search for '//' using '..//..'  I even went back to version 1.0 and the same behavior is there as well you can search for '//' using '..//..'

-Ray

Ray -

I probably wasn't clear when I said that I couldn't find use of the "/" in the user guide.  I wasn't referring to it's primary use regarding "not" ... I was referring to its use as an escape character to find the literal character following it.  

I was asking if that specific point was documented.

As for the // not working, I guess that will just remain a mystery as to why I originally could not use it.  What I had done was set up some records for import to Sesame.  Some of the "remarks" fields contained paragraph marks within the field.  In order for this not to be misinterpred as a new record, on import to Sesame, I did a search and replace of the paragraph marks with //. I thought I would then simply search for the records containing // and replace it with paragraph returns.  

I know that when I did my search it did not retrieve the records and I started over using something else.  In any case, it is clear that it does work ... and I may have had another "problem" that I didn't take into consideration.

Thanks!

Ray

Mea culpa and thank you for making the point.  Somewhere my message(s) went bonkers referring to \ and or /

In any event, page 235 is what I was looking for and I don't know why I missed it the first time.

Thanks

Quote:


You are both right. Mark meant if in a field you know there is a single period then it does not need to be escaped. You are searching for a period anywhere in that field in which case yes it needs to be escaped otherwise Sesame will see '.....' as '..' '..' '.' which is ending with a period as Sesame has no way to know that you want the middle period to be ignored unless you escape it.

Quote:


but a retrieve spec of

Mary..A..Lister..Billingsham..Wadsworth

would also retrieve

MaryAppleListerBillingshamWadsworth
Mary Joe Fred A Lister Billingsham Wadsworth
Mary Ann Clister Billingsham Fred Wadsworth
MaryAListerBillingshamWadsworth
Mary Ann Fred Joe Bob Sue Widlister Spencer Bob Billingsham Robert Sean Billy Barb Don John Lou Ginger Wadsworth

so to retrieve only the record whose field contains "Mary..A..Lister..Billingsham..Wadsworth" you would use a [

-Ray

Hi -

I'm getting close; however, I do not see the "problem" with max and min.  I am aware of the fact that I can use it to get a number of records such as max 5 or min 3 or whatever.

However, I do not see the affect that has on my searches.

If I enter Max, I retrieve all records with Max (and nothing else) in the field.  (Likewise with Min)

If I enter ..Max.. I retrieve all records that contain, anywhere in the field, the letters Max.  (Likewise with Min).

So, I am confused about when they need to be given "special" consideration in the situation I have described.

As far as I can tell the [] also works fine with single or wild card searches whether searching for either the left bracket or the right bracket or both. 

Can you give me any illustrations of where these characters won't work "properly" in a retrieve spec?

Thanks!

Aha!  Got it.  Thanks!

Did you see that I (thinking I could beat your reply - foolish me) modified the preceding note to include a comment about the brackets?

Well, I've got to put this aside for awhile and, unfortunately, I have not gotten a clear understanding of how the

[]
{
}

work.   (Grrr - and I don't understand why the forum won't let me separate the left and right brace, no matter what I try!  lol)

Other than that, the document is fairly complete, so I am going to e-mail it to you and would appreciate feedback on making it more viable for others to find it useful.

Thanks!

Quote:


Spencer,

I just talked to Mark and neither of us received the document as of yet.

-Ray