As anyone who has programmed Q&A or Sesame is aware, @Error will return the most recent error. But it only indicates that there has been as error (an din Q&A it is limited to the "X" commands). Some time ago I put @ErrorType() into Sesame 2.0 - that returns the type of the error that happened as an integer. Today I added "@ErrorString(type as int) as string" that returns an error string based on the integer passed in (presumably the same integer that @ErrorType() returned).

I also finished work on a command one of the Forum member asked for: @RegexReplaceString(expression as string, str as string, replacement as string) as string. This command accepts a regular expression, a string (that may match that expression zero of more times) and a replacement string that will replace those portion of the "str" that match the expression. This returns a string with the replacements. The original "str" is left unchanged.

So, for example:

var aa as string

  aa = @RegexReplaceString("m", "my name is mark", "p") // This will return a string: "py nape is park" because it was told to replace all of the "m"s with "p"s.

  aa = @RegexReplaceString("m.*k", "he is mark", "peter") // This will return: "he is peter" because it was told to replace any portion of the string that starts with a "m" and ends with a "k" with the word "peter".

  aa = @RegexReplaceString("^m.*k$", "my name is mark", "no it is not") // This will return: "no it is not", because it was told to replace the portion of the string that is at the beginning of the string ("^") and starts with "m" and has a "k" at the end of the string ("$") - thus it replaces the entire string.
 

Today, Ray made a new SBasic command for 2.0: "@PrintAFormAsHtml(filename as string) as int" that will print the current form as a HTML file (web page) to the filename specified. This allows you to print a form as HTML, and then (for example) attach it to an EMail using @SendMail and send that web page via email.

I also put in a speed optimization for @FormFieldValue and FormFieldValue when accessing Table View subform. If the optimization survives alpha testing (let's hope), it will make table subform access a lot faster and have no "flashing".

Quote:


Bob,

It works the same way as @Replace(). For example, say your command is

A = @RegexReplaceString(B, C, D) 

The command is going to search for B in C and replace it with D and then return the Altered String to A. The original string C is unaltered and the altered value is in the returned string A. So to do what you are asking you would want to use something like the code below.

C = @RegexReplaceString(B, C, D) 

-Ray

Quote:


The no flashing may not be earth shaking or all that exciting to most, however I can tell you from real world experience this improvement would be an incredible aid in not freaking out the users. I thank you whole heartedly for attempting this improvement!

Thanks

If you are looping through the subform to retrieve values from each record, to get a total cost of items sold for example, there will be an easier way in 2.0. I believe it is also significantly faster. These few lines

Var vList as String
Var vGrand as Double

vList = @FormGetValues("LineItems", "Total")
vGrand = @SumListValues(vList) 

do the same thing in 2.0 that the following lines do in 1.1.3

Var vList as String
Var vGrand as Double
Var vLoop as Int
Var vCnt as Int

vLoop = 1
vCnt = @FormResultSetTotal("LineItems")
vGrand = 0

While vLoop <= vCnt
{
	vGrand = vGrand + @ToNumber(@FormFieldValue("LineItems", "Total", vLoop))
	vLoop = vLoop + 1
} 

-Ray