Say you have a situation where the view leading key is a number, this by itself poses no problem. However, when you try to access this view from the Web using something like this:
Then the funs begin ......
It seems that you have to use a string in the first column (the sorted one) so you go ahead and use @Text(<Your_Numeric_Key>) ,if you do that things get no better because the @Text function remove the leading zeros and the result looks like this:
6 60 600 601 61 610 699 7 70 700 71 710 719 72
However if you use a formula like this one:
@Repeat(" "; 5 - @Length(@Text(<Your_Numeric_Key>))) + @Text(<Your_Numeric_Key>)
(The 5 stands for a key up to 99999. If you expect a bigger key, use a bigger number) The formula adds leading blanks so the result in nicely adjust and the result looks like this:
6 7 8 9 10 11
In order to use the StartKey= we have to add leading blanks: The full code for the Java script stuff is to big to fit here but it comes down to this:
query.value = " ".substr(1,5 - query.value.length) + query.value ; window.opener.location.search= "?OpenView&StartKey=" + query.value + "&Count=10&" ;
Note: query is the field the user will fill to get to the required key.
This was first published in August 2001