[Lantica Software Support Center] Recently Changed Articles

Will Sesame run on my operating system?

Thu, 21 Feb 2013 13:25:58 GMT

Sesame is a 32 bit application that runs on the following operating systems:

Windows 95
Windows 98
Windows NT
Windows 2000
Windows ME
Windows XP
Windows Vista (32 bit)
Windows Vista (64 bit as a 32 bit application)
Windows 7 (32 bit)
Windows 7 (64 bit as a 32 bit application)
Windows 8 (32 bit)
Windows 8 (64 bit as a 32 bit application)

As well as:

Linux (for Intel)

What are the minimum system requirements to run Sesame?

Mon, 10 Dec 2012 14:59:53 GMT

Sesame requires a Windows 95, 98, NT, ME, 2000, XP, Vista, Windows 7, Windows 8, or a Linux (for Intel) operating system. Minimum RAM requirements are the same as those required by the operating system. However, it is a good idea to have a total amount of RAM that is three times the size of your largest database. For network use over a LAN (local area network) or WAN (wide area network), Sesame requires installation of the TCP/IP (standard Internet) protocol on the network. The network server must be capable of running a Windows or Linux (for Intel) program on itself.

Change the state of a Checkbox from tri-state, to bi-state

Wed, 25 Apr 2012 15:51:47 GMT

Checkbox Layout Elements (LEs), by default, are tri-state: Yes (click to check), No (click to uncheck), and Unknown/Undecided (click to raise box). The following code example makes your checkbox bi-state (Yes/No), with "Active" being the name of your LE:

If @IsBlank(Active) Then
{
	Active = 1
}

Summarize all of the Layout Elements and their properties in an application

Wed, 18 Apr 2012 16:36:49 GMT

From the design menu in Sesame Designer, choose "Document Application" under the "Application" folder. Enter or select a filename and click Accept. This will produce an HTML file summarizing all of the elements of your design and their properties. This is a quick way to produce an overall view and is useful when writing X-Commands, for example, as a means to reference the elements in your application.

The resulting summary is organized into sections. Each section contains information about a different portion of your application.

Application Values - shows application settings such as Name, Unique Number, Image Path and Application Filename
Start Up Programming & Form - Shows startup form. Indicates whether this application has programming in On Application Open event
Global Values - Lists Global Values and their current values
Groups - Lists Security Groups, User IDs in the groups, and if they have passwords
Databases - Lists databases in your application. Each database shows a list of fields in that database and includes its properties, such as name and data type
Forms Summary - Lists Forms in your application. Each Form shows its name and database to which it's bound.
Reports Summary - Lists Reports in your application. Each Report shows its name and database to which it's bound.
Forms Detail - Detailed documentation for each Report including sections, section properties, elements, element properties, programmed events, attached specs, and security settings.
Reports Detail - Detailed documentation for each Report including sections, section properties, elements, element properties, programmed events, attached specs, and security settings.

All of the settings for the summary page's look-and-feel use CSS (cascading style sheets), therefore you can easily change things such as font and color by creating a CSS file and placing it in your current working directory. (See Create a CSS file to change the look-and-feel of "Document Application" summary elsewhere in this section of the Knowledge Base)

Also, see @StringArrayElementList in the Sesame Programming Guide - this function returns a list of all the elements on your Form. If you need to loop through all of your elements for reasons such as printing your values, or setting all the form elements to be read only, this function gives you everything you need.

Example:

Var vMyStringArray as String
	// vMyStringArray will equal a semicolon separated list
	// of Element names. Ex: "Last;First;Company;Address"
	vMyStringArray = @StringArrayElementList()

The Anatomy of a Sesame Application: Terminology

Tue, 10 Apr 2012 16:34:35 GMT

A Sesame application consists of one or more databases that are in some way related - such as a Customer database, an Orders database, and an Inventory database. A database consists of all the records, and all the forms (as well as optional sub-forms) and reports that show these records. For example, an Orders database might consist of all the order records, the order form and the Orders By Month report.

A layout is a form or report. Since Sesame is form-based, you will create your databases by building and editing layouts (or forms). It defines how you will look at and use the parts of your information.

A layout element is anything you put on a layout or form. Sometimes referred to as an LE, they can be purely cosmetic (such as a line or box), display data from your database records, display the result of a calculation, or let you change information simply by clicking or making a selection from a pick-list. Layout elements are bound to the fields whose information they display.

A field is a component of a database and is where Sesame actually stores your data, such as a telephone number. A field is not unique to a specific form. The same field can be displayed on different forms.

A record is a logical collection of fields. A record is displayed in a form. A form displays one record at a time.

For example, an Orders record may have fields for OrderDate, CustomerName, and ShipToAddress. It is rare in Sesame that you will work with an actual field. Normally, you will work with layout elements. A layout element that displays the value (content) of a field is said to be bound to that field. The only time that you will need to deal with an actual field is if you change its data type or its name.

For more information on the anatomy of a Sesame application, see Appendix 4: Advanced Concepts as well as the "Terminology" section under the Designing a Sesame Application chapter in the Sesame User Guide.

Summary:
An application, which consists of two files â€” application.db and application.dat â€” is comprised of one or more databases each with one or more forms and optional subforms. Forms and subforms are both comprised of layout elements. Most of those layout elements will be bound to fields.

Data is stored in fields.

Fields are displayed on forms using layout elements, which can be thought of as placeholders for those fields.

A layout element is unique to a specific form, and a form is defined by its elements.

A field is not unique to a specific form. The same field can be displayed on different forms.

Layout elements are bound to the fields whose information they display.

Creating Subforms in Your Application

Tue, 10 Apr 2012 16:29:44 GMT

Subforms are a way to view Records from a second database while in the Form of a master database - so that you can see Records from both databases at the same time. Therefore, you will need at least two databases in an application before you can create subforms, each based on a different database in the same application. (If you are unclear about the differences between a Sesame "database" and an "application", see The Anatomy of a Sesame Application: Terminology, elsewhere in this Knowledgebase, or consult your Sesame User Guide.)

You don't need to create relationships between databases before using your Subform. Sesame creates these relationships for you when you add a Subform to a Main Form.

Because Subforms are dynamic, you can edit data, delete records and add records in a Subform.

Step one is to create a new database for the subform. (If you are not familiar with creating new databases/forms, or just need to brush up, see "Designing a Sesame Application" in the Sesame User Guide.)

To add a new Form, select Forms -> Add New Database. Enter the name for this new database and form (though the name of your form and the name of your database can be the same, it is not necessary). This opens up a new, blank Form. Use the Layout Element Adder to add the desired Layout Elements (or LE's). When you are finished, save your work. You now have both a new database and a new form. Close the design tab.

At this point, your menu tree should show the new database that you have just created and its new form at the same level as the original, existing database. It should be directly beneath the orignial and not indented. This shows that the two databases are independent.

Step two is to add the form you have just created to the original, existing form in your application as a Subform.

Open the main form or Parent Record (the original, existing form) in Designer. Click on the form where you want to place your subform. In the Layout Element Adder, select element type: Subform. The Bind Element To must remain Unbound. If you wish to label your subform, do so now with the text of your choice - this will appear above the subform by default, though you can move it if you wish. Click on the Add Element to Form button.

Sesame should now be displaying the Subform Settings dialog window. This consists of 5 sections, which control the way the subform and underlying linking mechanisms are established:

Select a Form - This dropdown menu lists all the eligible forms in your database. Select the form you wish to use as the subform.

Select Subrecord Type - This menu lists the available link types. Here, you will tell Sesame how to decide which records in the database are conidered children of the parent record. The two choices are Automatic (Natural Links) or Matching Field Values (Relational Links). For more on this, see the Sesame User Guide or the Knowledgebase article listed below.)

Select Records to Display - For both Natural and Relational Links you will see three sets of choices.

Make Natural Child Record: This is the most common choice. Records in the subform are automatically linked to corresponding records in the main/parent form. The correct child records will appear in the subform based on your settings. (If Relational Links is selected, this option changes to Show Related Child Records, but the same logic applies.) Child records can also be accessed by opening the subform by itself. In this case all the records are shown mixed together.

Show Existing Natural Child Records: If the main/parent database already has a subrecord database(s) with appropriate linking, they'll be listed in a dropdown menu here. If one of these is selected, Sesame will use a pre-existing relationship, as would occur if another subform had already been created (in other words, the same records from the database will be shown as in the subform that initially created the existing field definition).

Create a New Database with Shared Template: If this choice is selected it clones the selected form and database, but without any data. This is useful when you need to add a form as a subform, which does not already exist. The records added using this subform won't mix with records added using other subforms, even though the subforms look identical. "Shared Template" means that all databases/forms that share a template will be kept in synch. So, if you add an LE to one form, all forms will have that element.

Set Subform Properties - You must assign a Field Name to the subform, and, if applicable, pick the matching fields for a Relational Link.

Select a View - Here, you will select whether you want to display the records in the subform in Table or Form view. (Form view shows LE's arranged on the form just as it was designed, while Table View shows records in a spreadsheet-like view with rows and columns - this is the most common choice for a subform as you can view multiple records at one time in this view).

Click OK and your subform is now added to the form. You can now resize or reposition the subform on the main form to your liking. Make sure to Save the layout once you've got everything looking the way you want it to look! Reconcile or save your design. (See the Knowledgebase articles: Reconciling an Application and Reconcile Application Options for more info on the Reconcile process.)

Looking back at the menu tree, you will see that the newest database is now indented under the original,existing database, rather than being directly underneath it.

See also:

In the Sesame User Guide:

Section 3-Designing a Sesame Application, Section 5-Creating Subforms, Section 7-Navigating Forms, 13-Working with Subforms.

From the Sesame Quick-Start Tutorial:

Building an Application with Subforms (If you do not have these manuals, go to Lantica.com to download them -- See this Knowledgebase article Download Sesame Documentation (Guides, Manuals, etc.) for instructions on how to do so.)

Other Knowledgebase Articles:

Should I choose Natural or Relational Subforms?

Change the background color of an individual cell in a form/subform

Can I choose which Layout Elements are displayed on a subform?

Renaming a Subform in Sesame Designer

Accurately Adjust the Width of a Table-View Subform

Sum Up Subform Values

Post a Value From a Parent Form to a Subform

Universal and Simple Searches in Subforms

Moving Sesame to a New Computer

Thu, 05 Apr 2012 20:32:01 GMT

It may become necessary, at some point, to move Sesame from one computer to another or to add computers to your existing network. Even more likely, you may need to update your Sesame software. With each new version Sesame provides tools and techniques for making database management easier and more efficient. Because Sesame's developers, technicians and consultants work so closely with Sesame users, suggestions for improvement and fixes are constantly being tested and implemented. These developments are actualized in the form of newer Sesame versions.

Common concerns for Sesame users during these occasions include whether the installation CD is necessary and what happens to their settings and data.

If you do not have your Sesame installation CD for any reason, you may visit Lantica.com and choose from a number of options in the "Downloads" section. From here, you can download the newest version of Sesame.

Following the instructions below will allow your data to transfer seamlessly. Should you run into snags along the way there's always a way to find a solution ( Where Can I Find More Information, Such as Online Help, with Sesame and Sesame Designer?) check out some of the other Knowledgebase articles listed below, take a look on the User Forum, or contact Technical Support.

Moving Sesame is really quite painless. Because there is more than one configuration possible, however, differences in how to do so exist. Therefore, it may be necessary to make a few minor changes depending on your particular situation.

Standalone Single User:

With the default install the Sesame program files can be found accordingly: The Sesame program files are in the C:\Sesame2\Program folder. Data files are in C:\Sesame2\Data. Documents are in C:\Seame2\Docs. Settings and configuration files are in C:\Sesame2 folder. To move to a new computer follow these steps:

Copy the entire Sesame2 folder from your old computer (either by right-clicking on the folder and choosing Copy, or clicking on the folder and using the Ctrl-C shortcut). This will copy the contents of the folder, including all of its subfolders. Paste this folder directly onto your new computer's C:\ drive (either by right-clicking and choosing Paste, or using the Ctrl-V shortcut) if the two computers are connected via a network cable. You can also copy and paste to your new computer via a thumb-drive. There are no hidden or read-only files or folders.

On your new computer, open Sesame2 -> Program. Right-click on Sesame (not SDesigner) and choose Send to Desktop (Create Shortcut). This will create the shortcut on your desktop.
Alternatively, you may also right-click on your desktop and choose New Shortcut from this dropdown menu. In the location line type: C:\Sesame2\Program\Sesame.exe and click Next. Sesame will automatically set up the proper icons for your shortcuts. Name your shortcut Sesame.

Right-click on the shortcut you've just created and select Properties. In the Start In: box, change the words C:\Seseame2\Program to C:\Sesame2 (essentially, you're just deleting the "\Program"). This is critical, as this will allow Sesame to find its configuration files.

Repeat steps 2 and 3 of Sesame Designer (substitute sdesigner.exe for sesame.exe) and name the shortcut Sesame Designer.

Multi-User Client Server Installation:

There are two different processes for this case - one for the server and one for the client computer(s). They are similar to the steps used for standalone systems, with some changes in the shortcuts.

Copy the entire Sesame2 folder from all computers - both client and server (either by right-clicking on the folder and choosing Copy, or clicking on the folder and using the Ctrl-C shortcut). This will copy the contents of the folder, including all of its subfolders. Paste this folder directly onto your new computer's C:\ drive (either by right-clicking and choosing Paste, or using the Ctrl-V shortcut) if the two computers are connected via a network cable (for both client and server). You can also copy and paste to your new computer via a thumb-drive. There are no hidden or read-only files or folders.
If you are only installing new clients, just copy the folder from the old to the new clients. If you are only putting in a new server, just copy the folder from the old server to the new server.

Find the network name of each of the clients and the server by right-clicking in My Computer on each machine and finding the line telling you the Computer name (or by right-clicking on the Sesame shortcut on the old computer(s) and choosing Properties).
For a new server installation: On the new server, create a new Sesame Server shortcut by right-clicking on your desktop and choosing New Shortcut from the dropdown menu. In the "location" line, type:

C:\Sesame2\Program\Sesame.exe -Server NameOfServer

(where NameOfServer is the network Computer Name of your server) and click Next. Name your shortcut Sesame Server and click Finish.

For new client installations: After copying the old client Sesame2 directory to the C: drive on each new client computer, create a new shortcut on the desktop by right-clicking and choosing New Shortcut from the dropdown menu. In the location line type:

C:\Sesame2\Program\Sesame.exe -Client NameOfServer

(where NameOfServer is the network Computer Name of your server) and click Next. Name your shortcut Sesame Client and click on Finish.

Right-click on your new shortcut and choose Properties. Change the words in Start in: to read C:\Sesame2, by removing the \program.

See these other Knowledgebase article for more information:
My machine name has spaces in it. How can I get Sesame to start a server on this machine?
What does Client/Server mean?
What do I need to let multiple users connect to my database?
Can I run more than one Sesame server?
What does the message "Failed to create a local socket: Unknown" mean?
How many clients can connect to a Sesame server?
Do I have to buy a separate program to run Client/Server?
Troubleshooting Client/Server Connection Issues
Reconfiguring Norton Security Suite To Allow Client/Server Connections

Creating and Using a Lookup Table

Tue, 03 Apr 2012 14:49:19 GMT

A fast and easy way to store and retrieve frequently used information during a data entry session.

A Lookup Table is a table of values stored in memory as an array. It's like having a small database within your database. It can contain information that's frequently needed during a data entry session, such as a state sales tax rates, shipping zones, discounts rates for different order levels, or state or province abbreviations.

The example below shows one method. In this example, a few state names are stored in the table along with their abbreviations and (imaginary) tax rates.

Create your Lookup Table array in the Global Code section of the form as a stat (static) variable. This way, it is available to your form element programs during the entire data entry session:

/* Declaring a "Lookup Table" array with 50 rows and 3 columns. The array can store 50 x 3 or 150 values, populated below. The table/array goes into the form's Global Code, while the programs that access it are connected to form elements and their events. */ stat LU1 as array{50, 3] of String LU1[1, 1] = "AL"; LU1[1, 2] = "Alabama"; LU1{1, 3] = "5.67" LU1[2, 1] = "AK"; LU1[2, 2] = "Alaska"; LU1[2, 3] = "0.00" LU1[3, 1] = "AR"; LU1[3, 2] = "Arkansas"; LU1[3, 3] = "6.25" LU1[4, 1] = "AZ"; LU1[4, 2] = "Arizona"; LU1[4, 3] = "6.50" // and so forth for the rest of the states

With this array available to the form's elements, you can use programming to retrieve the information you need.

The following On Element Change program for the State Abbrev element looks for a match on the state abbreviation. If it finds it in the table, it fills the State Name and Tax Rate. The loop is stopped as soon as a match is found. If no match is found by the time the loop expires, the user is notified, the lookup elements are cleared, and the cursor is returned to State Abbrev:

Var i as Int Var foundit as Int /* The "Lookup Table" array was created and populated in Global Code. Now run a loop routine in the array until it finds first match on the State Abbrev field and returns the corresponding values to the other fields. */ If State Abbrev <> "" Then { Foundit = 0 State Abbrev = ToUpper(State Abbrev) i = 1 While (i <= 50) And (foundit = 0) { If LU1[i, 1] = State Abbrev Then { State Name = LU2[I, 2] Tax Rate = LU1[i, 3] foundit = 1 } i = i + 1 } If foundit = 0 Then { @Msgbox("'" + State Abbrev + " ' not found in table.", "", "") Clear(State Name, Tax Rate) } }

Another way to populate (fill) a Lookup Table is to have your programming read in a delimited external text file, parse the values in it, and distribute those values to the array. This way, when you want to update the information in the table, you simply edit the text file - you don't have to update your programming unless the number of columns and/or rows exceeds the array declaration. See the Parsing a Delimited File and Importing Records with Programming Only examples elsewhere in the Knowledge Base or in Appendix 2 of the Sesame Programming Guide.

This, and other programming examples, can be found in Appendix 2 of the Sesame Programming Guide.

Importing Records Using Programming Only

Tue, 03 Apr 2012 14:48:23 GMT

Automatically add new records to a database by importing them on-the-fly from a delimited ASCII file.

The following program uses Sesame's CreateNewRecord() command to automatically add new records to a database. It reads a delimited (ASCII) file and parses and distributes its data to the elements in the new records. It can be launched from a command button on the form as an "On Element Entry" program. This program accommodates any delimiter you choose to specify, as well as a "value" qualifier such as double quote marks. The only requirements are a consistent delimiter and a carriage return separating each record in the text file. See the comments within the program for more details.

Note: When using a program like this, be careful to ensure that your programming parameters match the delimited text file you are importing. Otherwise, you could wind up with "garbage" records in the database. Test programs such as this on a copy of the database before being used in the actual database.

It is recommended that you use Sesame's import/export facilities for the routine importing of delimited text files into a database. (See the section on importing data in the Sesame User Guide and the Export/Import programming to/from a file article elsewhere in the Knowledge Base for more information.). The program below showcases Sesame's ability to process delimited text files and create new records from them with programming alone, as well as its uses for loops and arrays.

/*
Sample delimited text file parser program. Parses a delimited text file and creates new database records from it. Expects text file named C:\Sesame2\addresses.txt. Change to suit. Maximum 30 values per record (change to suit) in format such as:

"Tim Jones", "123 Main St", "Irvine", "CA", "92566"

-or-
Tim Jones;123 Main St;Irvine,CA;92566

This program expects Name, Address, City, State, and Zip fields. Change to suit.

A consistent field delimiter is required along with 1 record per line in the text file.
*/

var t as array[30] of string // Change to suit var vFileHandle as Int var vLine as String var counter as Int var nn as Int Subroutine parseline() var i as Int = 1 var vq as String = @Chr(34) // value qualifier (") var fd as String = ", " // field delimiter // Initialize the Array values for each new record line For i = 1 to DimLimit(1, t) T[i] = "" Next // Reset Array Count i=1

/*
If text file does not contain a 'value qualifier' (vq) char such as quote (") then do not specify a value for vq in the above declare.
*/

If vq <> "" Then { If @Left(vLine, 1) - vq Then { vLine = @Replfir(vLine, vq, "") } If @Right(vLine, 1) = vq Then { vLine = @Repllas(vLine, vq, "") } }

/*
Use a delimiter unlikely to be part of any value in case actual delimiter is a comma or other character that could be part of value.
*/

vLine = @Replace(vLine, vq + fd + vq, "|") While @Len(vLine) > 0 { T[i] = Split(vLine, "|") i = i + 1 } End Subroutine //####### MAIN PROGRAM ####### If @AskUser("Import C:\Sesame2\addresses.txt file", "and create new database records?", "") Then { If not FileExists("C\Sesame2\addresses.txt") Then { @MsgBox("Sorry.", "Couldn't find Addresses.txt file.", "") } Else { vFileHandle = fileopen("C:\Sesame2\adresses.txt") If vFileHandle >= 0 { FileSeek(vFileHandle, 0) While FilePos(vFileHandle) < FileSize(vFileHandle) { FileReadLn(vFileHandle, vLine) If @Len(vLine > 20 Then { Parseline() nn = @CreateNewRecord() Name = t[1] Address = t[2] City = [3] State = t[4] Zip = [5] Counter = counter + 1 } } FileClose(vFileHandle) @MsgBox("Imported " + counter + " records.", "", "") } } } Else { @MsgBox("Import operation abandoned.", "", "") }

This, and other programming examples, can be found in Appendix 2 of the Sesame Programming Guide

Parsing a Delimited File

Tue, 03 Apr 2012 14:46:44 GMT

The following sample program can be used as a template for programs to parse delimited files, as well as for programs that create a database Lookup Table from the values in a delimited text file. (See the Sesame Programming Guide, or the Creating and Using a Lookup Table article elsewhere in the Knowledge Base.)

The example below opens a semicolon delimited file (myfile.txt), reads through it, and parses and distributes its values.
For this example, myfile.txt contains the following data:

Tom;Bill;Jim;Edna Janice;Alec;Mark;Cliff Fred;Greg;Linda;Joanne;

The main program opens myfile.txt and sets the file position (FileSeek) to 0. A While loop is then started, its condition being that the file position (FilePos) is less than the length of the file (FileSize).

With each loop, the FileReadLn command reads the next line in the file, then the parseline subroutine is called.

Parseline prints the current line to the WriteLn window, then a For-Next loop parses the values in the line, distributing them into the six-element array named "t". Each parsed value is then individually written to the WriteLn() window. When finished, the WriteLn window displays the following:

Tom;Bill;Jim;Edna Tom Bill Jim Edna Janice;Alec;Mark;Cliff Janice Alec Mark Cliff Fred;Greg;Linda;Joanne Fred Greg Linda Joanne

See Importing Records with Programming Only (elsewhere in the Knowledge Base, or Appendix 2 of the Sesame Programming Guide) for a program that processes a delimited file and creates new records from it for the database.

/* Delimited text file parser sample program. Parses a semicolon-delimited text file named myfile.txt. Each line in the file expected to contain six values, in a format similar to any of these: Jim;Tom;Edna;Jane Jim,Tom,Edna,Jane Jim Tom Edna Jane Jim|Tom|Edna|Jane Set vDelim variable below to appropriate delimiter */ Subroutine parseline() var I as Int =1 WriteLn(vLine) While @Len(vLine) > 0 { t[i] = Split(vLine, vDelim) WriteLn(t[i]) i = i + 1 } End Subroutine vFileHandle = FileOpen("C:\Sesame\myfile.txt") If vFileHandle >= 0 { FileSeek(vFileHandle, 0) While FilePos(vFileHandle) < FileSize(vFileHandle) { FileReadLn(vFileHandle, vLine) If vLine <> "" Then { Parseline() } } FileClose(vFileHandle) } Else { WriteLn("Open failed: " + @Str(vFileHandle)) }

This, and other programming examples, can be found in Appendix 2 of the Sesame Programming Guide

Creating a Follow-Up Scheduler

Tue, 03 Apr 2012 14:45:14 GMT

Uses:

Program a form to display a follow-up menu on demand (making the need to manually type in a follow-up date unnecessary).

Learn how to do "arithmetic" with data values.

This sample program displays a pop-up selection list with the following callback intervals (change to suit):

Today, Tomorrow, Next Weekday, 5 days, 10 days, 15 days, 20 days, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday, User-entered date

Because the @PopupMenu() function displays the list in alphabetical order, the days of the week selections follow a A-Monday, B-Tuesday... format, to keep them together and in proper sequence.

When you make a selection (other than User-entered date), Sesame automatically fills the CallbackDate field with the date that corresponds to it, then moves you to the next element on the form.

The program can be attached to a Command Button's On Element Entry event.

var CallbackTemp as string CallbackTemp = @PopupMenu("User-entered date;Today;Tomorrow;Next Weekday;5 Days;10 Days;14 Days;20 Days;A-Monday;B-Tuesday;C-Wednesday;D-Thursday;E-Friday;F-Saturday;G-Sunday", "SELECT A CALL BACK DATE"); If @Instr(CallbackTemp, "-") = 3 Then { CallbackTemp = @Del(CallbackTemp, 1, 4); If @Dow$(@Date + 1) = CallbackTemp Then CallbackDate = @Date + 1 Else if @Dow$(@Date + 2) = CallbackTemp Then CallbackDate = @Date + 2 Else if @Dow$(@Date + 3) = CallbackTemp Then CallbackDate = @Date + 3 Else if @Dow$(@Date + 4) = CallbackTemp Then CallbackDate = @Date + 4 Else if @Dow$(@Date + 5) = CallbackTemp Then CallbackDate = @Date + 5 Else if @Dow$(@Date + 6) = CallbackTemp Then CallbackDate = @Date + 6 Else if @Dow$(@Date + 7) = CallbackTemp Then CallbackDate = @Date + 7 CNext } If CallbackTemp = "User-entered date" Then { @Msg("Type in the Callback Date and press Enter") Clear(CallbackDate) Goto CallbackDate } If CallbackTemp = "Today" Then { CallbackDate = @Date CNext } If CallbackTemp = "Tomorrow" Then { CallbackDate = @Date + 1; CNext } If CallbackTemp = "Next Weekday" Then { If @Dow$(@Date) = "Friday" Then CallbackDate = @Date + 3 Else If @Dow$(@Date) = "Saturday" Then CallbackDate = @Date + 2 Else CallbackDate = @Date + 1 CNext } If CallbackTemp = "" Then { ThrowFocus(CallbackDate) } Else { CallbackDate = @Date + Tn(@Num(CallbackTemp)) }

By placing the following optional program in the "On Element Change" event for CallbackDate, you'll be alerted if you accidently enter a date that's in the past, or too far in the future:

If CallbackDate > @Date + 30 Then { If @AskUser("Follow-up date is more than 30 days away!", "Do you really want to leave it that way?", "") Then { CNext } } Else { ThrowFocus(CallbackDate) } If CallbackDate <> "" Then { If CallbackDate < @Date Then { If @AskUser("Follow-up date is earlier than today!", "Do you really want to leave it that way?", "") Then { CNext } Else { ThrowFocus(CallbackDate) } } }

This, and other programming examples, can be found in "Appendix 2: Advanced Programming Examples" in the Sesame Programming Guide

Setting Up The Sesame ODBC (Open Database Connectivity) drive on Windows 7 (64-bit)

Tue, 03 Apr 2012 14:37:20 GMT

"How can I set up the Sesame ODBC drive on Windows 7, 64-bits? I am using a 32 bit program Crystal Report that I want to connect to Sesame with ODBC driver."

Be very careful in following these steps:

Copy sesodbc.dll from the Setup32 directory to C:\Windows\SysWOW64

Open the Windows Registry Editor

Make a backup of every key before you change it just in case

Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers

Right click on ODBC Drivers and choose New->String Value

Name the new string value "Sesame ODBC Driver", without the quotes.

Set the value data of that new string value to "Installed", without the quotes.

Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI

Right click on ODBCINST.INI and choose New->Key

Name the new key "Sesame ODBC Driver", without the quotes.

Right Click on Sesame ODBC Driver and choose New->String Value

Name the new string value "Driver", without the quotes.

Set the value data of Driver to "C:\Windows\SysWOW64\sesodbc.dll", without the quotes.

Right Click on Sesame ODBC Driver and choose New->String Value

Name the new string value "Setup", without the quotes.

Set the value data of Driver to "C:\Windows\SysWOW64\sesodbc.dll", without the quotes.

Right Click on Sesame ODBC Driver and choose New->String Value

Name the new string value "CPTimeout", without the quotes.

Set the value data of Driver to "", without the quotes.

Close the windows Registry Editor

Open a command line and browse to C:\Windows\SysWOW64\

Type "odbcconf REGSVR C:\Windows\SysWOW64\sesodbc.dll"

At this point, you should see the Sesame under the Drivers tab when you execute C:\Windows\SysWOW64\odbcad32.exe

Accurately Adjust the Width of a Table-View Subform

Tue, 03 Apr 2012 14:27:04 GMT

A Table-View Subform shows subrecords arranged in a table or spreadsheet-like view. There are scroll-bars to view other parts of the subform if it cannot be seen. A good example of this is the Cities subform within the Countries sample database provided with Sesame.

To correctly adjust the width of the subform table follow this simple formula:
Table row header width + Combined widths of subform LEs + Vertical scrollbar width

The Table row header width can be set using the sesame.ini file (see Appendix 7 of the Sesame User Guide for more information on all the possible .ini file entries):

TABLE ROW HEADER WIDTH: Sets the width in pixels of the record number column appearing in Table View and Table View Subforms.
Example: TABLE ROW HEADER WIDTH: 50
Default: 70

The Combined widths of subform LEs (layout elements) can be found by opening the form in SDesigner. Using the Countries.db as an example, you would open this database, and then open the "Cities" subform. There are two LEs in this subform: "City" and "Population". Under the Look/Position tab in the Property Viewer window, you will find each of the element's widths. Adding these measurements together gives you the combined widths of the subform LEs (City=140 + Population=80 = 220).

The Verticle scrollbar width on a table subform is 19.

Therefore, your formula, using the Countries.db as an example would be:

70 + 220 + 19 = 309

Thus, the Cities table-view subform will need to be at least 309 pixels long. (Almost every measurement in Sesame refers to the number of pixels, not including some widths in Reports and the PrintString command.)

Loop through all the LE's in a record to make them all read-only

Tue, 03 Apr 2012 13:51:10 GMT

#include "sbasic_include.sbas" var vElements as String vElements = @StringArrayElementList() If key < 1000 then { StringArrayAttributes(vElements, ATTR_ID_READ_ONLY, 1) } Else { StringArrayAttributes(vElements, ATTR_ID_READ_ONLY, 0) }

Documentation addition to @SpecCommand

Tue, 03 Apr 2012 13:46:35 GMT

The documentation for the @SpecCommand is insufficient in the Sesame Programming Guide. To run an export, this command requires more arguments than the documentation shows: (filename, custom separator, custom delimiter, tabbed, custom, no separator, ignore fixed, all, none, header). These correspond to the fields in the export dialog and the RunExportSpec command. Below is an example of how to export a set of data from a file. Spec is saved as "All Data".

#include "sbasic_include.sbas" var vRt as String /* Arguments: Filename Custom separator character Custom delimiter character Tabbed Use custom separator No separator Ignore fixed All None Use custom delimiter Header */ vRt = @SpecCommand(SPEC_OPERATION_LOAD, SPEC_TYPE_EXPORT, "All Data") vRt = @SpecCommand(SPEC_OPEATION_RUN, SPEC_TYPE_EXPORT, myfile.txt, ";", "", "0", "1", "0", "1", "0", "1", "0", "0")

Download Sesame Documentation (Guides, Manuals, etc.)

Mon, 02 Apr 2012 18:06:08 GMT

Your Sesame Application should be accompanied by all of the appropriate documentation upon download. Looking in your Sesame2 folder (usually found on your local hard drive - usually the C: drive - or wherever the application was downloaded to) you should see another folder named "Docs". In this folder you should see PDF versions of:

The User Guide

The Programming Guide

The Quick-Start Tutorial

The Q&A Translation Guide

Sample Word Merge Documents

To download these manuals, go to: Lantica.com/Support/downloads.html. You will need to enter your Customer Number and Password under the "Existing Users" section. (If you no longer have, or cannot remember, this information - contact Customer Service.

Once you have entered this information, you will be taken to a page with all of the available Sesame Plus downloads. For the documentation listed above, click on "Sesame 2.0 Manuals".

From here, you can also download the Sesame Errata and Changes (changes/corrections made to the existing Sesame documentation), the supplemental manual for the Command Button Menu (earlier versions of Sesame displayed menus in a tree-like style, whereas the newest version displays these menus in the Command Button style), sample Sesame Applications, Sesame dictionary files (for spell-check features), and the SBasic Include file for programming - among others.

Change the background color of a Checkbox depending on its value

Mon, 02 Apr 2012 17:58:23 GMT

You can accomplish this by programming the On Draw events of the checkboxes so that they change their background color depending on their value. This code changes the background color from white to gray depending on the value as you click the checkbox.

If @IsBlank(MycheckBox) Then { RGBColor(MyCheckBox, -1, -1, -1, 122, 122, 122) } Else { RGBColor(MyCheckBox, -1, -1, -1, 255, 255, 255) }

Export/Import programming to/from a file

Mon, 02 Apr 2012 15:34:17 GMT

You can export all of your programming in a Sesame database form to a standard text file for review or editing with any text editor. (Available on the File menu of the Program Editor) With some programming already in the form, select File/Export All to Text File. The Program Editor will display a Programming File dialog box. Name the file, adding the ".pgm" extension, and click OK.

The file that is saved is a plain text file. When editing the file outside of Sesame, it is important that you do not modify the heading line for each programming function:

** PROGRAMMING SECTION: [INVOICE #] {On Element Change] ** If @IsBlank(Invoice #) { Invoice # = @Number }

These are the lines that starts/end with **. They are the keys that tell Sesame where to place the programming when you import the file.

Importing is done the same as exporting. From the Program Editor's File Menu, select File/Import from Text File. The same dialog will display showing all files with a ".pgm" extension. If you gave your file a different extension, drop down the Show window and change it to display All Files.

Note: When you import a file into the Program Editor, any element listed in the imported file will overwrite any programming for that element in the editor. Any existing programming in an element/event programming slot in the editor that is not addressed in the imported file will remain unchanged.

See also: Save All Programs Attached to a Layout to a Disk File.

Save All Programs Attached to a Layout to a Disk File

Mon, 02 Apr 2012 15:31:59 GMT

You can optionally save all the programs attached to your current layout to a disk file without leaving the Program Editor. At any time, you can click the Program Editors File menu then click Exports All to Text File. Type a valid path, followed by a filename, then click Accept. Sesame will save all your programming to a plain text file, and include a heading for each separate program. In the following example, "Merge Letters" is the name of the programmed form element, and "On Element Entry" is the even that triggers the programming.

** PROGRAMMING SECTION: [Merge Letters] [On Element Entry] ** Var vLetter as String // The name of the selected merge letter Var vAllText as String // The entire text of the merge doc Etc...

When saving a program to file this way, name the file descriptively, so that you can later tell from the filename which database and layout it came from. Programming saved to a file in this manner can be easily opened in a text editor and then copied and pasted in the Program Editor of the same or another Sesame application.

See also: Export/Import programming to/from a file.

Create a Command Button that adds a bullet point in a field

Thu, 29 Mar 2012 18:13:39 GMT

After creating a Command Button on your Form add the following:

// Where the name of the field in which you wish to add the bullet is called "Notes" Notes = Notes + @Char(149)

SBasic Command Families

Thu, 29 Mar 2012 17:22:24 GMT

For a full list of the commands in each family, as well as examples see the Sesame Programming Guide

Array Commands

Formal Array Information

If you have declared an array (see the Variables section in the Sesame Programming Guide), commands such as Dims, DimLimit, ElementType can return information about its dimensions and type. Formal arrays require that you know in advance how large your array needs to be. In situations where the dimensions may vary, SBasic provides Dynamic Arrays (below).

Generic Arrays

A Generic Array is a reference to an existing array variable, and can be used to sort an array of any element type. Because it is a reference to the array, rather than the array itself, SBasic does not have direct access to it. Use a Generic Array only if you want to pass an array to another function as an argument.

SBasic includes a set of access functions that can get values from a Generic Array and set elements (values) in arrays. To get an idea of how these functions can be used in a subroutine designed for generic arrays, see the Using Generic Arrays sample program in Appendix 2 of the Sesame Programming Guide.

Dynamic Arrays

Dynamic Arrays are not variables that you declare. They are created, destroyed and accessed using SBasic functions. They allow you to create and use arrays that are sized at runtime based on factors such as field value or the result of a calculation.

String Arrays

In many situations, you might find StringArrays more intuitive and easier to deal with than the more formal arrays above. A StringArray is simply a list separated values (usually by a semicolon(;)).The String Array family of commands provides powerful tools to work with this list

var aa as string aa = "one;two;three;four"

This could also be a string array of field/layout element names, items for a selection list, etc. When creating string arrays, care must be taken to avoid spaces on either side of the semicolon separator.

Using StringArray commands you can: find/get one or more values out of a the list, add/edit/delete values in the list, change the order of the values in the list, find out how many values are in the list, strip the duplicate values out of the list, change the separator, or work with more than one list at a time.

Binary Math Commands

Allow you to operate on the individual bits in an integer. Very valuable for storing a series of yes/no choices in a very compact way.

Date/Time Commands

Use these to get and work with dates and times. Can be used to work with dates and times that appear in your own data, to return values from your local or server computer, as well as return portions of dates, such as the month or day of the week.

Sesame's internal date format is YYYY/MM/DD. If you use Text/String functions such as @Right or @Left to operate on dates, you should do so using this format. For example, to assemble a date which is the first day of the current month:

var vTheFirst as Date vTheFirst = @Left(@Date, 8) + "01"

Drawing Commands

Provide a number of low level drawing capabilities that allow you to draw directly on your forms. Typically, each command accepts an element and a set of pixel coordinates. The element serves as an "anchor" point for the drawing. The coordinates are relative to the position of this element, though the drawing is not limited to the confines of the element. Once a drawing is done, it will be remembered and refreshed when the form is drawn until you either clear the drawing or close the form.

Use drawing commands to provide information or visual representations of your data. Allow you to draw a variety of pictures, charts, predefined or user-defined shapes, text on your forms to provide messages/instructions, and control the color and font of drawn items.

Element Attributes Commands

These are the properties of layout elements, including color, position, etc. Provide tools you can use to control the look and some of the behaviors of your forms and reports as they are used.

Some Element Attribute commands operate on individual elements. These can be used to do things like make an element visible based on the User ID, change the color of an element, or set search criteria that will be filled in if you return to the Retrieve Spec. Many of these attributes already have separate commands (such as Visibility) that can be used, but this family of commands allow you to affect any attribute of an element by learning only one command, even if more attributes are added to elements later on.

// Change the label of an element #include "sbasic_include.sbas" Attribute(Company, ATTR_ID_LABEL, "Company Name") ForceRedraw()

Some Element Attribute commands allow you to work on a single element, while others operate on groups of elements. The latter allow you to affect settings like ReadOnly or Visibility on your entire form, or create custom Undo capabilities. For a list of modifiable element attributes, see the Sesame Programming Guide.

Element Reference Commands

Many SBasic commands require a reference to the actual element as an argument (as opposed to the value in that element), such as the Element Attribute and the User Interface commands. Element Reference commands return and work with references to the elements on your form, allowing you to create generic ways to provide element references to other commands that require them. Using this family of commands you can get and use a list of element names based on different criteria, get information about an element, and create and manage a reference to an element.

Event Management Commands

These provide control over how Sesame handles different events, such as a key being pressed. They also allow you to trigger your SBasic event programming without actually causing the event itself, for example, triggering a command button on a different form. With this family of commands you can control which keystrokes Sesame responds to, set a program to run on a timer, tell Sesame to notice additional events and run a program when they occur, get information about the last event, and trigger code on other forms.

External Database Application Management Commands

There are several families of External Database Application management commands or "X-Commands". Each family serves a different purpose, but they all operate on records in an external database - which may be in a different application, another database in the current application, or even the same database in which you are currently working.

Application Commands

Using the Application commands you can load (open) and unload external applications (DeferredOpenApplication, UnloadApplication).

XResultSet Commands

The XResultSet family of commands are the most flexible of the X-commands. If you are using any other commands for external database access, consider using these instead - they allow you to retrieve records, get and set values, delete records, reparent natural child records, and more. Because these commands access the database records directly, you don't need a form to do things like mass update a group of records, sort, or even run a report. They are also faster than the other X-commands, in most cases. The XResultSet commands also provide flexible search criteria.

To use these commands, first get a result set by using a command like @XResultSetSearch. Then, use the handle (a number that tells Sesame which group of records you want to work with) that is returned in the other XResultSet commands you call. When you are finished with a particular group of record, release your result set with XResultSetClose.

In addition to the above, using these commands you can also manage and navigate the records in a result set, get and change values in the result set records, and print a report in an external database.

X-Lookup Commands

The commands in the X-Lookup family retrieve values from an external database. They differ in the number of records they return, the number of values from each record they return, and what they do with the returned values. Some of the commands in this family include statement as well as function versions. Statements do not return a value. Functions make the retrieved value available. (For more on statements and functions, see the XLookup Commands section in the Sesame Programming Guide). The function versions of the "X" family commands are more versatile than their statement counterparts. For example, you can place an @XLookup function inside another function which then uses the retrieved value in further processing.

Note: If an "X" family statement cannot retrieve the external value, the target or destination element will remain unchanged. In contrast, if an "X" family function is unsuccessful, it will return an empty value (""), and the target of the assignment, if any, will be blanked. For this reason, these functions should be used with a conditional, such as If something <> "" (is not blank) then do the lookup. The something is usually a reference to the key in the current record that the program will use to find the matching external record. If the key is blank, the function will return a blank value. In such a case, you might not want the existing value in the current record to be changed (blanked).

Most of the commands in this family take four arguments - filename, key, ext_key, and source. A few also take a fifth - target. For an explanation of these arguments, see the Sesame Programming Guide.

With this family of commands you can: get a single value from the first matching record, get a single value from all matching records, get multiple values from the first matching record, and get multiple values from all matching records.

File I/O Commands

Allow you to create, append to, read and delete external text files from programming. With these commands you can generate entries in a log file when certain conditions are (or aren't) met, store and update subsidiary information in plain text files and bring them into your applications, read the contents of a delimited text file into an SBasic array, parse out the individual values, then distribute them to your database elements, as well as many others.

Financial Commands

The financial commands provide functions that are specific to financial calculations, such as loans, amortization and interest calculations.

Forms/Records Commands

Provide tools for you to manage your form values, subform values, records and result set navigation from SBasic. In general, commands that begin with "Form" or "@Form" allow you to specify a particular form. Those that do not - operate on the current form. This family of commands allows you to work with values or records, and navigate result sets.

Macros and Program Control Commands

Provides essential tools for automating your applications. Macro commands run a macro. Program control commands perform an automation task, or transfer focus and program control to another element.

Mathematical Commands

Provides a variety of mathematical functions. In addition to general math, these functions also include trigonometry, the ability to round numeric values, work with a list of numeric values, and generate a random number.

Menu Tree Commands

Enable the programmer to manipulate the items on Sesame's Command Menu tree. They allow you to control which commands are available and how they appear. They can be used in conjunction with @UserID, @Group and/or @UserParameter to make different menu choices available to different users.

Network Commands

These commands can be used to interact with websites, manage email, communicate with other Sesame servers, etc. They include email, alternate Sesame server, FTP, HTTP, and TCP/IP.

Operating System Commands

Allow you to interact with your operating system to perform tasks like file management and work with external programs.

Printing Commands

If you want to enhance an application by adding the ability for users to print merge letters, data, summaries, reports or formatted documents on-the-fly, this family of commands has the tools. These commands also include easy ways to merge your data into external documents and to print out your forms as well as controlling print settings, getting information about the current page, and selecting a printer.

Reports Commands

Most of SBasic works in almost any context, however, there are a few commands that apply specifically to reports. With these commands you can: make a report break based on whatever criteria you want, print out a report with or without user interaction, and postprocess the HTML in a report before it's sent to the printer.

Spec Management Commands

When you retrieve records, sort, import, export, etc., you use a Spec to set the options and specific behavior for the task. Outside of SBasic, you work with your Specs using the Spec Manager and the Spec Window. To work with your Specs in programming, you use the Spec Management commands. Each type of Spec has a pair of SBasic commands to load and run that type of Spec. There is also a single command that can load and run any kind of Spec, as well as performing a variety of other operations.

State Information Commands

"State" refers to "how things are now".
The State Commands are designed to answer questions such as:
"What mode am I in?"
"Which database is this?"
"Who is using me now?"
"What was the last Invoice Number used?"
"Are things changed/blank/unique?"
"What is my Form doing/allowed to do?"
"Did an error just occur?"
...and so on

Text/String Commands

Works with pieces of text, also called strings. Many SBasic programming tasks involve taking apart, putting together or otherwise manipulating text. These commands provide the tools to do so. With Text/String commands you can: measure, replace or remove part of, find something in, or change the look of the text, as well as produce particular characters.

Typecast Commands

Explicitly instruct Sesame to treat a particular value as a certain type. This is important when working with different types of values. Sesame will try to guess what you intend, but it is better to not make computers guess. These commands are useful for adding a piece of text to a number, concatenating two numbers together (rather than adding them), or subtracting dates to get the numbers of days between them.

User Interaction Commands

Communicating with the user is a common programming requirement. This command family offers the tools for getting and giving information. You can show a message, ask for information, offer a list of choices, make your own custom dialog box, and intercept keystrokes.

User Interface Commands

Provides tools to control how the Sesame interface looks and what options it offers you as you work. Also includes tools to control the look and behavior of your forms.

Element Commands

Affect elements that you create on your Forms and Reports. For example you can: change the look, size, position or behavior of your elements. You will also find additional commands for Text, Subform, Tab Group, Image, and List elements (such as Combo Boxes and List Boxes).(See the Element Attributes Commands for a wider range of controllable attributes.)

Menubar, Application Menu and Command Tree Commands

Affect parts of Sesame itself, including the menubar and the Command Tree. With these commands you can: show a panel of customized buttons instead of the Command Tree, change the Sesame Menu Bar or Command Tree state, and make a different Sesame Tab than the Application Menu the default Sesame Tab.

Sesame Interface Commands

Commands to change the behavior of the Sesame interface. With these commands you can: change the wording or language of Sesame interface elements, enable/disable warnings, change where a popup list appears, or play a sound.

Memory Menu Commands

List of values that appears when you press Alt-Enter. Normally, Sesame maintains this list for you, but you can control it with the commands in this section.

XML Commands

Because XML is an extremely common format, the XML files used and created by Sesame are useable in many other applications and programs, and vice-versa. Unlike HTML, which has a set of predefined tags, XML allows the author to define their own tags and notes, based on the needs of their application. These commands are able to read, create and parse XML file formats.

Natural vs. Relational Linking

Thu, 29 Mar 2012 16:42:07 GMT

Subforms offer two different types of linking: Natural and Relational. Natural linking is the default. While natural linking has the advantage being simple and fast, it is also inflexible. Once a record is set as a child of another record, it cannot be moved to be a child of a different parent record. The parent record can delete its children, or add more children, but it cannot share a child with another parent record. This can lead to data normalization problems. To remedy this, Sesame also provides relational linking.

Relational linking retains the same parent/child relationship as natural linking. The difference is in the method by which any particular parent record recognizes its child records. Where natural linking has a direct pointer from the parent record to the child record, relational linking provides the addition of Key Field set. This key field set stores the name of a field in the parent and the name of a field in the child. For any of the records that are of the correct type to be considered a child of a particular parent record, the data in the parent's key field and the child key field must match. Relational linking is even more flexible than a simple match between two fields. The parent's key field acts as "Retrieve Spec" and can use the same syntax as the retrieve form uses for that field type.

A simple way to understand the basic difference between relational and natural linking is to imagine two families: the Nevilles and the Orvilles. The Nevilles all hold each others hands. The Neville parents recognize their own children because they are holding the eldest child's hand. The eldest child holds the next oldest child's hand, on down the line of children to the youngest. The Nevilles are a naturally bound family. The Orvilles are relational. The parent wears a tee shirt that says "Orville" on the front. The children each have tee shirts that say "Orville" on the back. The parent knows the children by matching the names on the tee shirts.

Deciding whether to use natural or relational linking is simpler than understanding either. Just ask yourself if the data in the subform you are designing will repeat, unaltered, under more than one parent record. If the data will repeat, then it is wise to use relational linking, otherwise, or if in doubt, use natural linking. If the data must be unique to each parent, as in the example of logged transactions, natural linking is the natural choice.

For more information, see Appendix 4 - Advanced Concepts in the Sesame User Guide and the Knowledgebase article: "Should I choose Natural or Relational Subforms?".

Creating a drop-down Customer list to allow Users to choose contacts in other Forms

Thu, 29 Mar 2012 16:28:26 GMT

You may want to use something along these lines:

Var vList as String // Get all contacts from Contact form vList = @XlistValues(@FN, "Contacts!Contacts") // Initialize the Combo Box with unique sorted values PopulateListElement(TransName, @UniqueStringArray(@SortStringArray(vList,0)))

However, It is often a good idea to use variables in cases where you could (but probably shouldn't) nest functions. By using intervening string variables, you can use WriteLn to see the values of the variable during development to make sure that each step of the procedure is running the way you want it to:

Var vList as String Var vList2 as String Var vList3 as String // Get all contacts from Contact form vList = @XlistValues(@FN, "Contacts!Contacts") // Initialzie the Combo Box with unique sorted values vList2 = @SortStringArray(vList, 0) vList3 = @UniqueStringArray(vList2) PopulateListElement(TransName, vList3)

It adds visual clarity to the code, and makes it easier to debug. It may run a bit slower, but can be easily optimized after you know that it's working. Variables are many times faster and safer than elements. Only use an element to get the value initially, or to write the final result back.

Print all retrieved records using PrintString commands

Thu, 29 Mar 2012 16:04:33 GMT

"I love Sesame's ability to print all retrieved records and the available Printstring commands to print forms in my format. But, is there any way to combine these two? I have forms in my database that use "Print" command buttons, which include all the Printstring commands needed. Is there coding that can print all retrieved records using these Printstring commands?"

You can call your PrintString code in Mass Update.

or

ou can also loop through all your records in code by doing something like:

Var vCount as Int Var vLoop as Int Var vPos as Int SUBROUTINE PrintIt() // All your print code END SUBROUTINE vPos = @ResultSetCurrentPosition() vCount = @ResultSetTotal() For vLoop = 1 to vCount ResultSetCurrentPosition(vLoop) PrintIt() Next ResultSetCurrentPosition(vPos)

Debugging Your Code: Types of Errors

Thu, 29 Mar 2012 14:34:42 GMT

Errors are a part of programming. Knowing how to find and fix your mistakes is as important as knowing how to write the code in the first place. Logical Errors occur while your code is running. Syntax Errors occur while your code is compiling. The following is a more detailed description of the types of errors you will likely encounter while programming in Sesame. For debugging techniques, see this Knowledge Base article.
Syntax Errors
These are caught by testing your program in the Programming Editor. Syntax Errors occur when a section of code has been mistyped/misspelled, causing Sesame to misunderstand your instructions. A syntax error does not prevent you from saving a program. You can save your work - errors and all - and close the editor, the return to it later for further work. (Any programming is automatically, temporarily saved when you exit/close the Program Editor window. To permanently save all of your programming changes, click Save Layout Design on the Commands menu.) Examples of syntax errors include:

Misspelling an Element name

Misspelling an SBasic call

Leaving out a parenthisis

Calling a procedure with the wrong number or type of arguments

Logical Errors
Logical Errors occur when Sesame is doing exactly what you told it to, and that is the problem. These include :

Dividing by zero

Checking an incorrect condition

Incorrectly bracing conditionals

Looping forever

Type of Error Error Description Incorrect Correct
Warning Warning: layout element name [name] contains operator characters. The layout element name contains characters which make it illegal for use in programming. This is only a warning. If the layout element is not referred to in programming, this will not cause an error.
Syntax/Compile Missing closing quotes in String. Strings must have both opening and closing quotes. vStr = "Sesame vStr = "Sesame"
Syntax/Compile Missing close comment. Comments opened using /* must be closed. /* This is a comment /* This is a comment */
Syntax/Compile Unclosed character constant. Characters (Chars) must have both opening and closing single quotes. vChar = 'A vChar = 'A'
Syntax Declaration expected. Error occurs on or before the referenced line.
Syntax Statement expected. Error occurs on or before the referenced line.
Syntax Statement or End-Of-File expected Error occurs on or before the referenced line.
Syntax/Compile Subroutine name expected. A subroutine declarations is missing the name. Subroutine() Subroutine MySub()
Syntax/Compile Function name expected. A function declaration is missing the name. Function() as Int Function MyFunc() As Int
Syntax/Compile Variable declaration list expected. The program contains "var" without completing the declaration. var var vInt as Int
Syntax/Compile Static declarations after dynamic declarations are not allowed. All declarations of static variables must occur before any declaration of dynamic variables
Syntax/Compile Static declarations in functions and subroutines are not allowed. Static variables may only be declared outside of a function or subroutine
Syntax/Compile Variable name expected. Program uses a for-next loop with an invalid or missing index variable. For = 1 to 20 For vInt =1 to 20
Syntax/Compile Expression is expected. Program is missing an expression. vTotal = vTotal = (Unit * Price)
Syntax/Compile Parameter declaration expected. A procedure declaration has a trailing comma in the parameters area. Subroutine TestMe( var a as Int, ) Subroutine TestMe( var a as Int, var b as Int
Syntax/Compile Formal parameter declaration expected. A procedure declaration has an incomplete parameter. Subroutine TestMe( var ) Subroutine TestMe( var a as Int )
Syntax/Compile Subroutine or label expected. GoTo used without specifying target. GoTo GoTo CalculateMe
Syntax.Compile Label expected. GoTo used without specifying target. GoTo GoTo CalculateMe
Syntax/Compile Assignment operator expected. Statement missing an equal sign (=). vInt Units vInt = Units
Syntax/Compile Term expected Program contains an incomplete expression. vInt = 3 + vInt = 3 + 5
Syntax/Compile Symbol expected [symbol], symbol found [symbol2]. Usually indicates that an open symbol, such as (, occurs without a matching close symbol. [symbol] shows the found open symbol. [symbol2] shows the symbol found instead of the expected close symbol. If(vInt = 5 Then ...produces the error: Symbol expected [)], symbol found [THEN].
Syntax/Compile Direct reference for var parameter expected. The program attempts to pass a static value to a function or subroutine which is expecting a variable to be passed by reference. Example:
Function TestMe(var vInt as Int) as Int Return 5 End Function Var vInt2 as Int vInt2 = TestMe("test")

Syntax/Compile Label used as jump target but label definition is missing. GoTo statement references a label which does not exist in the procedure. Example: If there is no label defined as GoHere:, the following statement would produce this error.
GoTo GoHere
Syntax/Compile Type expected. A declaration is missing the type. var vInt as var vInt as Int
Syntax/Compile Type mismatch error (operation is not defined for the types of the operands). Program attempts to perform an operation which is illegal for the types of the operands. Example: if vFullName and vLastName are both type String, the following statement would produce this error because Strings cannot be subtracted from each other.
FirstName = vFullName - vLastName
Syntax/Compile Type mismatch error (types of formal and actual parameter must match for VAR parameter). The program attempts to pass a value to a function/subroutine which is of a different type than is declared for that function or subroutine. Example: The following code would produce this error because the type of the variable being passed is not the same as the type declared.

Function TestMe(var vInt as Int) as Int Return 5 End Function Var vStr as String Var vInt2 as Int vStr = "Test" vInt2 = TestMe(vStr)

Syntax/Compile Type mismatch (both operands must be of the same type). Both operands (specifies what data is to be manipulated or operated on) must be of the same type.
Syntax/Compile Boolean expression expected. Program expects an expression or value of the specified type.
Syntax/Compile String expression expected. String expression expected.
Syntax/Compile Numeric expression expected (int, double, char, bool, date, time). Program expects an expression or value of the specified type.
Syntax/Compile String type expected. Program expects an expression or value of the specified type.
Syntax/Compile String expected Program expects an expression or value of the specified type.
Syntax/Compile Unknown identifier. Identifier does not exist or is undeclared. Identifiers must be declared before they are used.
Syntax/Compile Loop invariants (FOR-NEXT-counter) must be simple local variables. Variables used to index loops must be declared locally.
Syntax/Compile GOTO not allowed here. Program attempted to use a GoTo to jump out of the current function or subroutine.
Syntax/Compile Navigation programming not allowed here. Navigation programming is not legal if running SBasic standalone.
Syntax/Compile Redefinition of identifiers is not allowed. Indentifiers may only be declared once within any particular scope.
Syntax/Compile Variable or function not defined. Variable or function does not exist or is undeclared. Variables and functions must be declared before they are used.
Syntax/Compile Array name expected. Program attempts to access a generic array using = instead of a generic array call, such as SetIntElement.
Syntax/Compile Number of dimensions does not match definition. The number of dimensions in the array does not match the array declaration.
Syntax/Compile Number of formal parameters does not match number of actual parameters. The number of parameters used does not match the procedure declaration.
Syntax/Compile Indexing operator [ ] not allowed on generic arrays. Program attempts to index a generic array instead of using a generic array call, such as SetIntElement.
Runtime Error Function does return a value. A function must return a value.
Function MyFunc() as Int End Function

Function MyFunc() as Int Return 1 End Function

Runtime Error Illegal type (operation not allowed). The operation is illegal for the data types. Example:
vString = "FirstName" / "LastName"
Runtime Error Division by zero. Program attempted to divide by zero. Example:
Bonus = Salary / 0
Runtime Error Array not dimensioned. An array was declared, but not dimensioned.
Runtime Error Wrong number of dimensions in array access. Program uses an array accessor function using a different number of dimensions than the array being accessed. Example:

var MyArray as Array[10, 2] of Int MyArray[5] = 3

Runtime Error Max. array index negative while creating array. An array has been declared with a negative dimension. Example:
var MyArray as Array[-1] of Int
Runtime Error Array index zero while accessing the array. The program attempted to access an array using an index of 0 (zero). Example:
vInt = vaMyArray[0]
Runtime Error Array index negative while accessing an array. The program attempted to access an array using a negative index. Example
vInt = vaMyArray[-1]
Runtime Error Array index overflow. The program attempted to access an array using an index larger than the array dimension. Example:

var vaMyArray as Array[10] of Int vInt = vaMyArray[15]
Runtime Error Runtime type mismatch while accessing an array. Program attempted to access a generic array using an accessor function for a different data type. Example: Attempted to access an array of type String using SetIntElement.
Runtime Error @CGR: pv and fv must have the same sign. Present Value and Future Value must have the same sign. vCGR = @CGR(100, -500, 10) vCGR = @CGR(100, 500, 10)
Runtime Error @FV: i must be >= -1;
@PMT: i must be >= -1;
@PV: i must be >= -1. Program attempted to use one of these financial functions with an interest rate parameter of less than -1
Internal Error Constant pool overflow.
Internal Error Runtime stack overflow.
Internal Error Internal error: Runtime stack underflow.
Internal Error Internal Error: Call stack empty while looking for invocation record.
Internal Error Internal Error: Invocation record not found on call stack.
Internal Error Internal Error: jump target not defined.
Internal Error Internal Error: variable name could not be defined.
Internal Error Internal SBasic Error. Contact Technical Support.

For information, see "Using the Programming Editor" in the Sesame Programming Guide.

Type of Error	Error	Description	Incorrect	Correct
Warning	Warning: layout element name [name] contains operator characters.	The layout element name contains characters which make it illegal for use in programming. This is only a warning. If the layout element is not referred to in programming, this will not cause an error.
Syntax/Compile	Missing closing quotes in String.	Strings must have both opening and closing quotes.	`vStr = "Sesame`	`vStr = "Sesame"`
Syntax/Compile	Missing close comment.	Comments opened using /* must be closed.	`/* This is a comment`	`/* This is a comment */`
Syntax/Compile	Unclosed character constant.	Characters (Chars) must have both opening and closing single quotes.	`vChar = 'A`	`vChar = 'A'`
Syntax	Declaration expected.	Error occurs on or before the referenced line.
Syntax	Statement expected.	Error occurs on or before the referenced line.
Syntax	Statement or End-Of-File expected	Error occurs on or before the referenced line.
Syntax/Compile	Subroutine name expected.	A subroutine declarations is missing the name.	`Subroutine()`	`Subroutine MySub()`
Syntax/Compile	Function name expected.	A function declaration is missing the name.	`Function() as Int`	`Function MyFunc() As Int`
Syntax/Compile	Variable declaration list expected.	The program contains "var" without completing the declaration.	`var`	`var vInt as Int`
Syntax/Compile	Static declarations after dynamic declarations are not allowed.	All declarations of static variables must occur before any declaration of dynamic variables
Syntax/Compile	Static declarations in functions and subroutines are not allowed.	Static variables may only be declared outside of a function or subroutine
Syntax/Compile	Variable name expected.	Program uses a for-next loop with an invalid or missing index variable.	`For = 1 to 20`	`For vInt =1 to 20`
Syntax/Compile	Expression is expected.	Program is missing an expression.	`vTotal =`	`vTotal = (Unit * Price)`
Syntax/Compile	Parameter declaration expected.	A procedure declaration has a trailing comma in the parameters area.	`Subroutine TestMe( var a as Int, )`	`Subroutine TestMe( var a as Int, var b as Int`
Syntax/Compile	Formal parameter declaration expected.	A procedure declaration has an incomplete parameter.	`Subroutine TestMe( var )`	`Subroutine TestMe( var a as Int )`
Syntax/Compile	Subroutine or label expected.	GoTo used without specifying target.	`GoTo`	`GoTo CalculateMe`
Syntax.Compile	Label expected.	GoTo used without specifying target.	`GoTo`	`GoTo CalculateMe`
Syntax/Compile	Assignment operator expected.	Statement missing an equal sign (=).	`vInt Units`	`vInt = Units`
Syntax/Compile	Term expected	Program contains an incomplete expression.	`vInt = 3 +`	`vInt = 3 + 5`
Syntax/Compile	Symbol expected [symbol], symbol found [symbol2].	Usually indicates that an open symbol, such as (, occurs without a matching close symbol. [symbol] shows the found open symbol. [symbol2] shows the symbol found instead of the expected close symbol.	`If(vInt = 5 Then ...`produces the error: Symbol expected [)], symbol found [THEN].
Syntax/Compile	Direct reference for var parameter expected.	The program attempts to pass a static value to a function or subroutine which is expecting a variable to be passed by reference.	Example: Function TestMe(var vInt as Int) as Int Return 5 End Function Var vInt2 as Int vInt2 = TestMe("test")
Syntax/Compile	Label used as jump target but label definition is missing.	GoTo statement references a label which does not exist in the procedure.	Example: If there is no label defined as GoHere:, the following statement would produce this error. `GoTo GoHere`
Syntax/Compile	Type expected.	A declaration is missing the type.	`var vInt as`	`var vInt as Int`
Syntax/Compile	Type mismatch error (operation is not defined for the types of the operands).	Program attempts to perform an operation which is illegal for the types of the operands.	Example: if vFullName and vLastName are both type String, the following statement would produce this error because Strings cannot be subtracted from each other. `FirstName = vFullName - vLastName`
Syntax/Compile	Type mismatch error (types of formal and actual parameter must match for VAR parameter).	The program attempts to pass a value to a function/subroutine which is of a different type than is declared for that function or subroutine.	Example: The following code would produce this error because the type of the variable being passed is not the same as the type declared. Function TestMe(var vInt as Int) as Int Return 5 End Function Var vStr as String Var vInt2 as Int vStr = "Test" vInt2 = TestMe(vStr)
Syntax/Compile	Type mismatch (both operands must be of the same type).	Both operands (specifies what data is to be manipulated or operated on) must be of the same type.
Syntax/Compile	Boolean expression expected.	Program expects an expression or value of the specified type.
Syntax/Compile	String expression expected.	String expression expected.
Syntax/Compile	Numeric expression expected (int, double, char, bool, date, time).	Program expects an expression or value of the specified type.
Syntax/Compile	String type expected.	Program expects an expression or value of the specified type.
Syntax/Compile	String expected	Program expects an expression or value of the specified type.
Syntax/Compile	Unknown identifier.	Identifier does not exist or is undeclared. Identifiers must be declared before they are used.
Syntax/Compile	Loop invariants (FOR-NEXT-counter) must be simple local variables.	Variables used to index loops must be declared locally.
Syntax/Compile	GOTO not allowed here.	Program attempted to use a GoTo to jump out of the current function or subroutine.
Syntax/Compile	Navigation programming not allowed here.	Navigation programming is not legal if running SBasic standalone.
Syntax/Compile	Redefinition of identifiers is not allowed.	Indentifiers may only be declared once within any particular scope.
Syntax/Compile	Variable or function not defined.	Variable or function does not exist or is undeclared. Variables and functions must be declared before they are used.
Syntax/Compile	Array name expected.	Program attempts to access a generic array using = instead of a generic array call, such as SetIntElement.
Syntax/Compile	Number of dimensions does not match definition.	The number of dimensions in the array does not match the array declaration.
Syntax/Compile	Number of formal parameters does not match number of actual parameters.	The number of parameters used does not match the procedure declaration.
Syntax/Compile	Indexing operator [ ] not allowed on generic arrays.	Program attempts to index a generic array instead of using a generic array call, such as SetIntElement.
Runtime Error	Function does return a value.	A function must return a value.	Function MyFunc() as Int End Function	Function MyFunc() as Int Return 1 End Function
Runtime Error	Illegal type (operation not allowed).	The operation is illegal for the data types.	Example: `vString = "FirstName" / "LastName"`
Runtime Error	Division by zero.	Program attempted to divide by zero.	Example: `Bonus = Salary / 0`
Runtime Error	Array not dimensioned.	An array was declared, but not dimensioned.
Runtime Error	Wrong number of dimensions in array access.	Program uses an array accessor function using a different number of dimensions than the array being accessed.	Example: var MyArray as Array[10, 2] of Int MyArray[5] = 3
Runtime Error	Max. array index negative while creating array.	An array has been declared with a negative dimension.	Example: `var MyArray as Array[-1] of Int`
Runtime Error	Array index zero while accessing the array.	The program attempted to access an array using an index of 0 (zero).	Example: `vInt = vaMyArray[0]`
Runtime Error	Array index negative while accessing an array.	The program attempted to access an array using a negative index.	Example `vInt = vaMyArray[-1]`
Runtime Error	Array index overflow.	The program attempted to access an array using an index larger than the array dimension.	Example: var vaMyArray as Array[10] of Int vInt = vaMyArray[15]
Runtime Error	Runtime type mismatch while accessing an array.	Program attempted to access a generic array using an accessor function for a different data type.	Example: Attempted to access an array of type String using SetIntElement.
Runtime Error	@CGR: pv and fv must have the same sign.	Present Value and Future Value must have the same sign.	`vCGR = @CGR(100, -500, 10)`	`vCGR = @CGR(100, 500, 10)`
Runtime Error	@FV: i must be >= -1; @PMT: i must be >= -1; @PV: i must be >= -1.	Program attempted to use one of these financial functions with an interest rate parameter of less than -1
Internal Error	Constant pool overflow.
Internal Error	Runtime stack overflow.
Internal Error	Internal error: Runtime stack underflow.
Internal Error	Internal Error: Call stack empty while looking for invocation record.
Internal Error	Internal Error: Invocation record not found on call stack.
Internal Error	Internal Error: jump target not defined.
Internal Error	Internal Error: variable name could not be defined.
Internal Error	Internal SBasic Error. Contact Technical Support.