Sign Up for Training |
Jet Express Support |
Jet Reports Company Site
Jet 365 Financials
Jet Professional
Jet Enterprise
Submit a Request
Give Feedback

What's New in Jet Enterprise



Overview of the New Features and Improvements in Jet Enterprise 2017 (17.5)

Jet Enterprise 2017 (17.5) introduced a number of important new features and improvements. Below is an introduction to the changes made in this version of Jet Enterprise.


Feature Description KB Article
Redesigned Interface

The first thing you’ll notice when you open the 17.5 release is a new and improved user interface. With the redesign, the interface is less cluttered and gives more room to what matters: your data

Internet Connection through Proxy Server

With the wide use of web-based data sources, more of our customers are likely to be using proxy servers.  Jet Enterprise 17.5 now supports the use of a Proxy Server for web traffic.

Support for Internet Traffic through Proxy Server
Support for SQL Azure

Jet Enterprise 17.5 introduces support for using Azure SQL Server for your repository, data warehouse, and staging databases

Using SQL Azure For Repository, Data Warehouse And Staging Databases
Improved Conditional Lookup Fields

The performance, behavior and usability of Conditional lookup fields (the feature that allows you to use a field from one table on another) has been substantially improved.

Improved Conditional Lookup Fields
More options for delete handling In JDM 17.5, you have more options for tracking records which are removed from history-enabled tables. More Options for Delete Handling
Type "0" fields now supported Jet Data Manager 17.5 includes support for type 0 fields - which are ignored by the JDM. Use Type 0 Fields on History-Enabled Tables
General Usability Improvements

In addition to the redesign of the interface, Jet Data Manager 17.5 contains a myriad of smaller improvements to improve the usability.

General Usability Improvements
Deprecated Feature Support Some older features in the Jet Data Manager have lived out their usefulness and continue to exist in the product solely for backwards compatibility. While backwards compatibility is a high priority for us, such features will now included the suffix
"(deprecated)" to help you manage your use.
Feature Deprecation


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request