The Wizard The new version of ODBCFace comes equipped with a new development wizard that will reduce the distance between you and a fully functional maintenance model to three fast and easy steps. Creating a maintenance model for a master table is now going to be as easy as 1, 2, 3.   In the ETL world there is no tool as fast and easy as ODBCFace. Worried about XML? One of the new OLE DB providers developed by Microsoft® is called MSDAOSP (DAO Simple Provider). When used with the data source Microsoft XML Control, OLE DB has the extraordinary ability to let you access XML data. You can download or interact with any XML enabled web site.   You are going to be able not only to retrieve information from static XML pages but also to retrieve, post, modify and delete dynamic XML data with ease. Enhanced Security The new ODBCFace setup allows you to enable or disable development capabilities.   This provides a method in which you can prevent an user from modifying the ODBCFace models and prevent running the Setup or Debug forms. To provide additional security, ODBCFace profile files could be kept in a read-only folder in the system or on a network drive.   In addition, if you have any glitches with a model, press Ctrl + Alt + r, get to the Register form and enable yourself for development temporarily.   If you have the authorization key of course…     From ODBC to OLE DB Although it still supports ODBC connectivity, the new engine of ODBCFace is based on the Microsoft® Data Access Components MDAC 2.7 Library.   This library is naturally supporting OLE DB data providers. OLE DB is Microsoft®'s strategic low-level interface to data across the organization.   OLE DB is an open specification designed to build on the success of ODBC by providing an open standard for accessing all kinds of data. OLE DB does not impose any specific limitation on the query syntax or the structure of the data exposed as long as it can be retrieved in tabular form.   Example of OLE DB providers currently available include, but are not limited to, IBM DB2/400 and DB2 Universal, SQL Server, Oracle, Jet (Access), ODBC, OLAP Services, Data Mining Services and Directory Services.   OLE DB and ODBC are part of the Microsoft UDA (Universal Data Access) strategy for data access and you can find more information on it at the Microsoft® UDA site http://www.microsoft.com/data/. Automated Execution The new version of ODBCFace now supports an unattended execution mode.   In unattended execution mode, you can double click on any ODBCFace workbook and open the model, execute all the defined interface steps and exit from Excel. All with one double click.   Nevertheless, there’s more. You can use Windows scheduler, or any other sophisticated scheduler, to schedule your interface job at the time you want them to run. Connection Properties The new version of ODBCFace allows you to embed properties retrieved from the connection itself in your SQL statements.   With simple syntax like XXUSER = '%MDAC(User ID)' you will be able to flag an updated or inserted record in J. D. Edwards® with the user currently connected to the system. Execution Log It’s now possible to have ODBCFace keep a log of the interface activity.   At the individual model level a log ca be created or appended to. I is also possible to create a new log and to specify if this log is to contain every detail of the interface (down to the individual SQL statement executed and error occurred). This feature will help you troubleshoot any problem your users may have running ODBCFace models and will come in handy when running unattended interface models.

Home