Skip to the content Back to Top

If you have new staff, students or volunteers who may need to search or add records to your databases, it is a good idea to have guidelines on data entry protocols, and some instructions on how to search effectively. However printed documents are often lost or not readily accessible, so we recommend adding notes and hints to the DB/TextWorks forms themselves. These can be as brief or as lengthy as you need – we have designed some forms for clients with incredibly detailed instructions.

The databases in all our DB/TextWorks kits feature query screens with searching hints in a text box at the bottom:

SearchScreenHints

We also often add brief instructions in a text box right next to each field on data entry screens. We indicate in the label formatting whether a field is required (red) or has a validation list (underlined).

In the screenshot below we have also divided a long data entry screen up into sections with black textboxes, and resized boxes to indicate the length of a typical entry.

EditScreenHints

The DB/TextWorks Form Designer is a drag and drop WYSIWYG interface so quite easy to learn. If in doubt use Save As to make a copy of an existing form while you experiment.

When adding either a form or a text box, parameters such as size, label position and font are inherited from the box above of the same type. You can also click on a box, and right click to copy and then paste to create multiple matching boxes for your hints.

These simple conventions and the addition of hints can make the search and data entry experience much easier for your new or irregular users! We still occasionally find clients just using the basic forms – taking advantage of these design capabilities can dramatically improve the usability of your database.

We can of course help you!  Contact us if you’d like any training or assistance with designing any DB/TextWorks screens.

Inmagic has released version 17 of the its popular desktop database management system, DB/TextWorks, with several new features, such as:

1. Undo Record Deletion

Ah, we've all done this... deleted a record we didn't mean to, or worse, clicked Batch Delete instead of Batch Modify and wiped out hundreds or thousands of records. Oops. Of course, we all have robust backup systems (right?) so we've been able to recover from our mistake without too much grief.

But now we can recover deleted records with a couple of clicks within DB/TextWorks. This new feature needs to be specifically enabled for each DB/TextWorks user (in Tools > Options).

Once active, whenever you delete a record, a copy of it is first written to a CSV text file in your User Files directory. This applies both to single record deletions and to batches. The file is stored for 5 days, so you have a short window in which to realize your mistake, but there is no limit to the number of records that can be stored this way. There is then a new menu option (Records > Undo Delete Record(s)) to recover the most recently deleted records, working backwards through all deletions.

One important caveat is that fields in your textbase which are Automatic Number, Automatic Date and similar system-generated fields will most likely not be restored to their original values, but rather set to new ones. For example, if you have a field that stores the date a record was created, when you undo record deletion, the restored records will have today's date as the created date. A small price to pay for the ease of recovering from a mistake, though.

Savvy Windows users who want to rely on this as an even longer term insurance policy could get around the 5 day storage period with a script that runs nightly on their PC to copy the CSV text files to some other folder for permanent storage, where they won't be deleted. (Contact us if you need help with something like that).

2. Search for Duplicate Records

A new entry on the Edit menu, "Browse Duplicated Terms", opens the Query Choices Browser with a new radio button option, "Duplicated Terms", selected. This shows all entries in the selected field which are present in more than one record. In other words, where the Term Index shows all entries, this omits all those that appear in a single record only.

This feature is useful for fields that ought to be unique, such as Call Number in a Library Catalogue or Accession Number in an Archival Accessions or Descriptions database. You,ll quickly be able to see, find and correct inappropriate duplicates.

3. Send Report as Mail supports specifying alternative port

This feature is handy if you use a service such as SendGrid to send bulk emails to addresses stored in a DB/TextWorks databases, as these sorts of services often require that you use a specific port, rather than the email default port of 25.

Bug Fixes

Also addressed in this release are fixes several issues that appeared in the previous one:

  • Specified sort in Genie report is ignored.
  • Dead URL Link Checker: cannot handle TOC info (pound sign) in URL. The checker is more robust, but some URLs still may not be handled correctly (Due to obsolete WinHTTP stack in 32-bit window).
  • Copy Special operation may not include all data in a record.

If you upgrade from a version prior to 15 directly to 17, be sure to read the instructions about the necessary upgrade to your textbases as well as the software. If you're already using version 15, 15.5 or 16, you'll have done this already.

Customers with a current Inmagic maintenance subscription will receive emails from advantage@inmagic.com with instructions for downloading this release. As always, contact us with any questions about this new release, to check the status of your maintenance subscription, or for help upgrading.

Inmagic has released version 16 of the very popular and long-standing DB/TextWorks database management system, and the companion WebPublisher PRO web search interface. Several new features, as well as issues fixed from previous releases, continue to make this software great value for our clients.

New features include:

  • Sorting – When specifying sort fields, you now have the option to sort empties last. Before, records where the sort field was empty could only be listed first or omitted. Since this option does not change the perceived number of records in the report, it is also available for the textbase Default Sort Order and for WebPublisher reports.
  • Form Designer – WebPublisher reports can now easily link from a small image on a web page (a thumbnail) to the full size image. The new option is on the HTML tab of the Picture Box Properties dialog box.
  • Adding/Editing Records – When editing a Link field, a new type of box permits you to browse the values in a field other than the Link field, making it easier to select the record you want to link to. For example, you can display the list of Borrower Names, and clicking a name will paste that user’s employee ID into the Link field box.
  • Select All (Ctrl+A) – This keyboard shortcut now behaves as it does in nearly every other product. You can use it to select all the text in a box, all the boxes on a form or screen, all the text in the Command Query window, or all the annotations on an image. In previous releases, Ctrl+A was used for Redo. Redo now uses Ctrl+Y. 
  • Edit Textbase Structure – The Edit Fields dialog box has two new features:
    • Sort Field List by – This feature permits you to sort the Field List by Field Name, or by Field Type.
    • Hide <Deleted> Fields – This option permits you to hide the <Deleted> items so they do not clutter up the display.
    • Note: Both are display-only features to make it easier to find and work with the fields you want to modify. Neither affects the actual field order specified in the structure.

Other issues addressed include:

  • Print Images – If a textbase has multiple Image fields, and you print only the images from a specific field, blank pages are no longer printed for any images specified in the other fields.
  • Report window – Addressed an issue with the records sometimes not being visible past the first page when you held down the mouse scroll wheel then dragged the mouse.
  • Send Report as Mail – Improved the handling of multiple email addresses when using the "Mail to addresses specified in records" feature.
  • Textbase Information – Addressed an issue where longer short date formats caused the year to be truncated in the "Current date" specified at the top of this display.
  • Toolbar icons – The icons for Vertical Tile and Horizontal Tile were backwards in previous releases. This issue has been corrected, and the options have been renamed to "Show Windows Side by Side" and "Show Windows Stacked" to make their behavior clearer.
  • Form Designer – Addressed an issue with the Box Properties dialog box crashing when a box included an extremely large Fixed Text or Added Text string (usually HTML).
  • Textbase Information – Removed Windows Group Memberships from Textbase Information and "About this Computer System".
  • WebPublisher Browse Choices – The buttons have been optimized; for example, we've added an "Add & Close" button so that users no longer need to click "Add" then "Close".

If you upgrade from a version prior to 15 directly to 16, be sure to read the instructions about the necessary upgrade to your textbases as well as the software. If you're already using version 15 or 15.5, you’ll have done this already.

Clients with a current Inmagic maintenance subscription will receive emails from advantage@inmagic.com with instructions for downloading this release. As always, contact Andornot with any questions about this new release, to check the status of your maintenance subscription, or for help upgrading.

Inmagic has released version 15 of DB/TextWorks, WebPublisher PRO and DB/Text for SQL

Highlights of this release include:

DB/TextWorks

  • New Field Type: Rich Text. The Rich Text field type permits you to change fonts (font name, size, color, bolding, italics, etc.) within a single field, align text, create bulleted lists, and so on. 
  • New Field Type: Call Number. When records are sorted by a field using the Call Number field type, Call Numbers are sorted the correct order.
  • Email Enhancements: Email dialogue more closely resembles sending mail from an email client, and includes fields for additional message text and a signature.
  • Limits on the number of fields, characters in field names, linked textbases, forms, query screens, and many other features have all been increased.
  • Substitution Lists: Additional Field Types now support Substitution Lists: Call Number, Code, Image, Link, and Number.
  • Import Document. Improved IFilter text extraction for PDF files, especially those with text in the margin. Also, line breaks are added after each period-space (". ") to improve readability.
  • HTML, XML and Text Encoding enhancements for increased compatibility.
  • As well as features for publishing to the web, assorted small fixes, and a few older, less-used features removed.

More information is available in the DB/TextWorks Version 15 Read Me.

WebPublisher PRO

  • Issues addressed with the InmagicBrowse app, and new features added for publishing to the web from DB/TextWorks.

More information is available in the WebPublisher PRO Version 15 Read Me, as well as the DB/TextWorks Version 15 Read Me and the DB/Text for SQL Version 15 Read Me.

DB/Text for SQL

  • In addition to the features added to DB/TextWorks and WebPublisher (see above), DB/Text for SQL is now supported on SQL Server 2014.

More information is available in the DB/Text for SQL Version 15 Read Me.

 

All clients with a current Inmagic maintenance subscription will be receiving emails from Inmagic with download instructions for this release.

This release also includes a new version of the PowerPack (Importer, Checker and Updater apps), popular for automating data import and full-text extraction and indexing, as well as the search-only DB/SearchWorks version of the software.

A new version of the ODBC driver is expected within the next couple of weeks.

 

Important Notice

Upgrading the Inmagic software to version 15 requires a change to textbase structures. Once made, only version 15 of DB/TextWorks and WebPublisher PRO will be able to access the databases. Therefore, plan to upgrade all servers, workstations and databases at once.

Clients using the ODBC driver should not upgrade to version 15 of DB/TextWorks, nor upgrade their textbases, until version 15 of the ODBC driver is released.

 

Please consult the system requirements and supported OSs and web browsers for DB/TextWorks, DB/Text for SQL and WebPublisher PRO,  available on the Inmagic Extranet.

 

If you have a current Inmagic maintenance subscription but have not received a notification email in the next week or so, please email advantage@inmagic.com with your serial number and email address so it can be resent. Please also remember to let us know if your contact information has changed so we can update our records and pass this on to Inmagic.

As always, contact us with questions, for assistance with this upgrade, or to renew an expired Inmagic maintenance subscription.

Dbtext for SQL tests out okay on SQL Server 2012. My specific test environment was:

  • Client
    • Windows 8 x64
    • Inmagic Dbtext for SQL 13, SQL authentication
  • Server
    • Windows Server 2008 R2
    • SQL Server 2012 SP1 Standard (11.0.2100)
    • Mixed mode enabled
    • TCP/IP protocol enabled
    • Firewall enabled, TCP 1433 port open
Categories

Let Us Help You!

We're Librarians - We Love to Help People