Getting the Most from Lantica's Sesame Database Manager
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . August 18, 2019  7:09 pm. PST
T H E  Q U A R T E R L Y  G U I D E  F O R  S E S A M E  U S E R S / D E V E L O P E R S

2 0 1 9
Vol. 16, No.3
(New issues posted quarterly by 5th of month)

(Insider password required)

Previous Issue Summaries


Have you checked out our Sesame Add-Ins lately?
Could be there's something you could use


July 2019 issue summary. . . [order code JUL19]

Natural or Relational Linking? ― Or Both?
When creating a parent/child database, it’s usually best to go with Sesame’s default natural or automatic linking to keep all the child (subform) records firmly attached to their respective parent records. But it can pay dividends to add the rarer relational linking to the mix as well.

Label Sheets that Really Aren't ― A Trashy Tale
A county agency charged with overseeing trash collection printed out weekly lists of residents qualified for special services. But these weren't your everyday lists. Designed like mailing labels sheets, Sesame had to follow the exact same Q&A pattern to prevent any confusion during the transition.

Follow the Flashing Arrow
There are many ways to draw attention to something on a data entry form when conditions warrant ― making something change color, flash, pop up or move in a way that can’t escape notice. An old standalone Q&A database in a town’s building department came with handwritten instructions (taped to the computer monitor, no less) for running a particular report several times each day. All that would change in Sesame.

Everything on Tabs ― Except...
When using a tabbed interface on a Sesame form, it makes sense to place the primary or most often used search fields above the tab group where they will always be in view. Here's why.

Custom Letterhead on Reports
A special report required the city’s letterhead at the top of the first page only. They hadn’t been able to do that in Q&A except by putting a single sheet of letterhead paper into the printer tray prior to printing. In Sesame they wanted the report— letterhead and all — to print to plain paper. Sesame prints reports to the default browser. And browsers all have their quirks. Here's how we made all the major ones behave in the same predictable way.

_______________You ask. We answer.

  • Navigating Tabs — GoTo, ThrowFocus, GotoTabPage. What to do when you need a sensible navigation scheme in a group of  tab pages.

  • Where are My WordMerge Files? — The boss takes home a copy of the database on a portable drive each night and wonders why the WordMerge won't work.

  • Save Temporary Values for Later Use — When variables and the like need to persist during a Sesame session.

  • Moving Sesame to New Computers — A full rundown on how best to go about it.

  • Copy Sesame Reports Into Excel — We've covered this  extensively over the years. But there are some differences in Windows 10 with Excel and the Edge browser.

  • Totals-Only Quick Reports  — Can it be done? Options?

_______________Technical tidbits you can use today

  • Checkboxes as Unique ― A Different Behavior. The polar opposite of setting a normal data field to Unique. But the difference can work to your advantage.

  • Increase Report Break Spacing ― To create some additional vertical space between group breaks in a Sesame report, you might add another Group or two. But there's an easier way to get the same result.

  • Got Some ^J's in Your Data?Yuck! How did those get in there? Make them go away!

  • Clarification on Save As HTML in Last Month’s Issue.


(Insider password

How to Copy Programming Code from
Inside Sesame to paste into Sesame's Program Editor

You can copy programming code from Inside Sesame Acrobat PDFs and paste it into your Sesame Program Editor.

Select the code with your mouse, then Right click on the selected text and choose Copy to copy it to the clipboard. (If the program continues to another page, do that page separately.)

In Sesame's Program Editor, select Edit | Paste (or press Ctrl-V) to paste the copied code into the appropriate LE/Event slot.

Inside Sesame programming examples may inadvertently contain styled quotes. If these are present, you'll get a lexical error when you Test the program. You'll need to replace these styled quotes with the plain straight quotes the Program Editor requires.

Sesame doesn't like slanted (styled) quotes: “SomeValue″
Sesame likes plain straight quote marks: "SomeValue"

To convert any styled quotes to plain quotes in the Program Editor:

  1. Copy one styled opening quote to the clipboard.
  2. Open the Program Editor’s Search | Replace box.
  3. Paste (Ctrl-V) the styled opening quote into the Find field.
  4. Type a plain quote (") in the Replace field.
  5. Click Replace All.

Follow the same steps to replace any styled closing quotes with plain quotes then retest the program.