October 2018 issue
summary. . . [order code OCT18]
Report-Running — A Case Study After running their reports the same way for 20 years, an
engineering company’s transition to Sesame turned up a few rough spots.
Lucky for them that their new system had options and capabilities far
beyond their old one, including ways to make their routine
report-running easier and more flexible than ever before.
Find Past & Future
Dates by Whole Months
A date range was needed for a lookup that would
find all the records where the date in a date field was 15 months to
the day back from the record’s date. As if that wasn't enough, a
routine was also needed to find a future expiration/warranty date in
years (2 years, or 24 months, for example) based on a known initial
Fields for Precision Printing A Q&A-to-Sesame migration turned up a printing challenge. Work
orders for the company’s outside service people had been printed the
same way for 20 years — on a form-fed dot matrix printer to pricey
custom-designed three-part NCR-style forms. Now that the company was
in Sesame with Word Merge, the challenge was how to print the same
data to precise, tamper-proof X and Y positions on the same form-fed
Counting Lines, Words & Characters
in a Multiline Field The data in a multiline field had to be limited to 16 lines
because that’s all that would fit on the output medium. Too much text
would overwrite other areas of the form and could trigger premature
page breaks. A line counter was added just below the field to alert
the user when there was too much text in the field to safely print.
Printing Records to PDF Common in the Q&A days, a company might have a purchase order
database designed to look and print like a PO that they would
snail-mail or fax to the supplier. Ditto for sales orders and routine
invoicing. Increasingly these days, suppliers and customers accept or
even prefer an “electronic” document (a PDF). We walk you
through the process of generating a PDF from a database record.
Where Are My Merge Records? — Right
there. You're just missing a little something.
Combine Multiple Merge Letters
to Email — Is it possible to group merged documents in a way
that they can be emailed in a single file?
Sesame and ISP Change —
What you might need to know Sesame-wize should you ever change
Internet service providers.
Export/Import Multiple Apps
— Or "How do I keep two or more apps in
Mass Update, Include All the
Rules — Mass-updating a field can put related fields out of
sync with the changes. Look before leaping.
Multiple Apps / Same
Server — What could possibly go wrong?
Set a Default Sort in a
Database — A handy refresher on a common request.
Recover Lost Records From a
Backup — And they just happen to be subrecords.
Merge Docs on Server — Yep,
that's where you want 'em in a multi-user environment.
Where are My Fields? —
"Let's see. The last time I was working on them...."
_______________Technical tidbits you can
See More Data in Table Subforms
― The easy way to see lengthy information in subrecords without
having to reach for the F6 key. (This trick is really cool.)
Read-Onlies & Restrictions ― Records were made read-only
after posting them, but they still had to be browsable. Problem was,
the browsing triggered restrictions.
The Strange Case of the Cranky
Retrieve Spec — A curious issue came up with a report Retrieve
Spec that worked fine in Q&A, but not so fine in Sesame. Desperate
times call for desperate measures.
Rename/Copy/Delete a Poorly-Named
Report — If you managed to translate a Q&A report with a slash
in its name, trouble will follow should you ever need to rename,
copy or delete that report.
(Insider password required)
How to Copy Programming Code from
Inside Sesame to paste into Sesame's Program
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
(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.