Hi

Still playing with the trial version as I await delivery in the UK...

I like to use the XUSR function to form a pick list from a partially completed field (perhaps I should now say element). If typing the name of someone already in the database I could, with Q&A,  type the 1st three letters and hit a carriage return to produce a list of all those beginning with those letters. I can't seem to get this to work with Sesame. If I set the start and end fields with letters in inverted commas, no problem. If I then reprogramme and use the same (partially completed) element as my start and end I get no values at all unless I leave the element blank. If I set start as my partially completed element and the end as "Z" I get a list from my partially completed element onwards.

Any help would be appreciated.

Peter

Thanks for that Alec. I'm glad I'm not going mad!!

Best wishes

Peter

This is one of those areas where the developers had to make a decision - be backwards compatible or forward thinking. Frankly, it had to be one or the other. Sesame uses the same rules and query mechanism as regular form based queries when performing the "X" commands (XLookup, XPost, XUserSelect, etc...).

While that does make Sesame's "X" commands very mildly incompatible with the same commands in Q&A, it does provide a great deal of flexibility and expansion. This is also the reason why, in ranged operations, specifying the same string for the upper and lower boundaries of the range can only find an exect match. In Sesame, setting both the lower and upper range as "R", tells the query engine to find all the records where the field is greater than or equal to "R" AND where the field is lesser than or equal to "R". The only value that can match that exact condition is one equal to just "R".

The advantage of this is that it allows a "true" range operation. In Sesame, if you set the lower boundary to "R" and the upper to "Rob", you will get all the records that start with "R" but not those alphabetically beyond "Rob", such as "Robert" or "Run". In Q&A , it is impossible to limit the selection in this way. For example, in Q&A the range "RAAA" to "RC" will match (incorrectly) "RCDDD".

Sesame also provides the ability to use the entire query syntax in any of the "X" subroutines and functions in any of the key or range fields, because it doesn't attach an "implied" wildcard onto either. That make its very easy to test a range operation usng the form itself:

>=lower & <=upper

If you want to get all the records that start with "R" - set the lower boundary to "R" and the upper to "Rzzzzzzzz".

This is fixed in release 1.0.1 - the upcoming release. In meantime, if you alter your code to read:

If @in (vFieldName, "..")  > 0 then
{      
    vStart = @left (vFieldName, @in (vFieldName, "..") - 1) + @chr(1)
    vEnd = @left (vFieldName,   @in (vFieldName, "..") - 1) + "zzzzzzz"
}

It should start to work. Let me know.

To Bharat and all interested parties, this problem has been fixed in 1.0.1, which is now available for download by licensed customers.

Bharat, I think you should have the fix for the problem in 1.0.1 - try removing the "@chr(1)". I believe it is no longer necessary. Just using:

v_start = LE_name
v_end = v_start + "zzzzzzzzz"

is working well for me here - using 1.0.1.