Getting the Most from Lantica's Sesame Database Manager
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . April 18, 2019  8:07 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.2
(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

 

April 2019 issue summary. . . [order code APR19]

What's Up With That 'Save Current Record As HTML' Option?
It's been staring at us from the  Commands panel since day 1. There’s even a programmable @PrintAFormToHTML version in the Sesame Programming Guide. Never used either one? Us neither — until a need came up. Turns out there's a whole lot you can do with this feature. Portable database records are just one example. Get a preview here: Print Records to HTML

Lock Him Up!
Naturally, a security services company had tight security on its own database. The salesman was another story. Good at sales, but not so much with a database. The boss didn’t want him anywhere near it. So when sales-related notes needed to be added to a customer’s record —and the office gals got tired of doing it for him — a little Sesame magic made everybody happy.

Tweak a Fields Text Size On-the-Fly
An office equipment/IT services company had a large multiline field for Systems Engineer Notes at the bottom of their Q&A invoice form. The maximum text volume in Sesame's counterpart accommodated the same volume. The problem in both was that more than 19 lines triggered an unwanted page break in the invoice printing. We fixed this in a way that allowed even more notes in the field without any spillover.

A Database of Databases
A company worked its inventory system in Q&A by creating a new directory each year with a bunch of starting databases. Records were copied and moved between these annual  databases and new records added. Given Sesame’s “Q&A compatibility,” they expected to continue doing things the same way they always had. But 100+ databases to begin with and another 10 to 15 every year wouldn't do. Time to change the whole thing.


_______________You ask. We answer.


  • Custom Fixed-Length Export File — This one goes way beyond a normal export routine. Something only a government agency would love.

  • Import Bombs in Newly Translated App — The #1 reason why imports fail and how to remedy the situation.

  • Searching on Parts of Numbers — Unique record-numbering in a database calls for some expert know-how when portions of those numbers have special meaning.

  • Sesame Opens the Wrong Database — Certain kinds of backup routines done a certain way can leave users scratching their heads — or worse.

  • Sesame Looks Different on Identical PC's — What could account for that?

  • Command Menu Mishap?  — Seemingly out of the blue the bottom of the Sesame Commands Panel became unusable. How'd that happened and what fixed it?


_______________Technical tidbits you can use today
 

  • Easier Global Values Updates ― A simple method admin personnel can use to update Global Values in Sesame Runtime.

  • PDF995 and @SendMail It’s All In the Timing ― What can happen when sending an @SendMail email with an attached PDF file that hasn't been completely rendered.

  • Simple Soft Restrictions — There’s a gentler middle ground that’s easier to implement, less intrusive and genuinely effective for normally conscientious data entry personnel.

  • A Fresh Take on Initial Values  ― Sesame doesn’t have the behavioral equivalent of a Q&A Initial Values spec, though it comes close. We show how to smooth out the rough edges.

  • The Strange Case of the Missing Data ― Following a routine Reconcile, it looked like all the data in the database had disappeared. Where'd it go? 

 


(Insider password
required)

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.