We have many reports using MS Access to report data to the State or for 401K plan census reports, etc. that require many of the fields in the Personally Identifiable Individual (PII) data. It makes no sense having to export the data using Visual Integrator to create an ODBC connection. Doing so makes the data far less secure!
We should not have to create a BOI script to access the data via ODBC (as suggested by Sage with an unsupported sample script) to extract the data. Again making the data less secure!
The product should use the ODBC Security events to provide an option to access this data via ODBC for use in Excel or MS Access! Every one of my clients uses ODBC access for State or other payroll reporting requirements. This is a fundamental loss of functionality with this 'upgrade'.
by: Casey S. | over a year ago | Payroll / Job Cost
Comments
Add permission to access PII to Sage Intelligence connections, as there is in Crystal Reports