Lantica Software LLC.
Learn more about Sesame Database Manager
I also, would like to compliment the Lantica team on their responsiveness and dedication. Where else can you get such quick help for a software product -- from the people who wrote it -- on Saturday and Sunday, no less. What other product is so willing to implement a new feature sometimes within days of a request?
Carl Underwood
- New England Antenna Service
 

Getting started with Sesame? Click here!
 
Home
Order Sesame
Products
Support
Contact Us
Company
Downloads
Q&A™
 
 
Email Address


Note: Your email address will be used only to notify you of updates and events related to Lantica and Sesame. Your address will not be sold or used for any other purpose.


Sesame Database Manager is compatible with Symantec Q&A. Q & A users will find that Sesame uses many of the same keystrokes, the same search syntax, and almost the same programming syntax as used in a Q&A database. Sesame can also translate Q&A databases. Find out more.


Inside Sesame - The Monthly Newsletter for Sesame Database Manager
Read a FREE issue!

 

Sesame Library | Field Types and Data Entry - Q&A vs. Sesame

One of the principal differences between Sesame and Q&A will be apparent as soon as you design your first database or import a Q&A database into Sesame. In Q&A, certain field types are "loosely" defined. For example, in date fields you can enter a valid date - or anything else you want. In the latter case, Q&A will give you a warning message that it can't reformat the entry to a valid date, but will allow you to keep it if you want. Likewise, in a Speedy-Unique field, Q&A will let you enter a non-unique value simply by overriding the warning. The same thing in time fields.

In Sesame this won't be the case. Date fields will accept only entries that are recognizable (or can be reformatted) as valid dates; unique fields will accept only unique values; and time fields will accept only valid times of day. You might feel that such "tight" restrictions are a step backwards. We feel it's the right way to go. Here's why.

If you force "September 00" into a date field in Q&A, you have just rendered that record invalid whenever that date field is used in a Retrieve Spec for a record search, report, or the like. In other words, if you then search for all your invoices dated August 1, 2000 or later, the "September 00" record will not be included. Since it's an invalid date format, Q&A can't find it. The same holds true for time fields.

If you force duplicate unique field entries and that field is used as the external key value in an XLookup from another database, Q&A is liable to retrieve information from a record other than the one you want. Q&A will retrieve the information from the first matching record it finds, and since the record order can vary from use to use, you can't be sure which record Q&A will find first.

The Sesame team feels that data integrity is far more important than the ability to enter data haphazardly. In Sesame, if you need a field where you can store anything, simply define the field type as "text" rather than "date" or "time" and Sesame will let you enter whatever you want.

(See Also Getting Your Q&A Data in Good Shape for Sesame)

  Learn more about Sesame Database Manager
I was very impressed when I got my copy of Sesame, to see such extensive PRINTED documentation. Not often you get this much paper with a software package. And, the manuals are on the CD, so you can use Adobe Reader (Free program) to search the manuals for topics you want to read about.
  T. J. Shuflin
Owner - Shuflin Services, LLC