|
First check the resellers page to see if
there is an authorized reseller in your area. If there is, then
contact this reseller for an on-site demo.
If there is not a reseller in your
area, Contact ReportsNow at
support@reportsnow.com or 303-693-6999. We
can setup an online demo with you.
Data Access Studio™ has significant advantages over UTB. You need Data Access
Studio™ if you need the ability to:
- Open Tables and Business Views
- Export data to Excel or other applications
- Calculate on the fly
- Perform any number of related table lookups from any grid (dynamic
table lookups)
- Visually create columnar and cross-tabular reports
- Printing with all the extras
- Format the data visually
- Save your formats
- Group, sort, total
- Get detailed information about tables and business views
- Filter with more powerful queries
- Load data faster
- More...
Data Access Studio™ has four ways to deploy to your enterprise:
- Full Client
- Citrix
- LAN Server
- HTTP Server
With the Full Client option. Data Access Studio™ has an automatic update system. The system
administrator simply updates Data Access Studio™ in a central location.
Every Data Access Studio™ workstation will pull the update the next time
the user opens Data Access Studio™. For those companies that use enterprise deployment software such as
Tivoli or ZenWorks, Data Access Studio™ deploys as an MSI package.
For the Citrix, LAN Server, and HTTP Server options, simply update the
server with the latest version of Data Access Studio™. The clients
simply connect and run!
Data Access Studio™ loads records over 2 times faster than UTB.
The user interface is fast, modern, and responsive.
Data Access Studio™ can view data from any ODBC and OLEDB compliant
table.
Data Access Studio™ is specifically designed to work with OneWorld®.
This means that Data Access Studio™ seamlessly integrates into the
OneWorld® system by leveraging OneWorld®:
- User security
- Data Dictionary
- Object Configuration Manager
- Data source configuration
- Specification information
DAS does the following to minimize any system performance degradation:
- Generates the highest performing query possible.
- Provides an "index assistant" which helps the user identify which
columns will generate the fastest query.
- Allows user to hide unnecessary table columns and save this as a
layout. DAS will only bring back the visible columns. This results in
reduced network traffic, reduced database utilization, and increased
speed.
- Allows an administrator to control which groups can do ad hoc queries
versus published queries.
- Consumes no JDE enterprise server resources.
Back to Top
All grid results are stored on
the local workstation (whether that workstation is a full client or a thin
client).
Back to Top
All calculations are
performed on the machine that runs the DAS Client.
On the Fat Client, all calculations are performed
on the user's workstation.
On the LAN or Web mode, calculations are performed on the
user's workstation.
On Citrix, all calculations are performed on the
Citrix server.
Back to Top
DAS connects using the JDE middleware. This
means that DAS will work with whatever OneWorld data sources you have set
up. Furthermore, in using the JDE middleware, DAS enforces the JDE
data access security.
Back to Top
Because DAS is read-only, it does not lock any records. It is up to the
particular database to make the query read-consistent.
Back to Top
Yes. DAS has both an error log and a trace log. Furthermore,
DAS uses the existing jde.log and jdedebug.log to trace the JDE middleware.
You can turn on the DAS error log in the following ways:
- Using the registry - turns log on or off for DAS sessions that run on
this workstation.
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\ReportsNow
- Set Log to 1
- The DAS.log is stored in the user's temp directory. (E.g.
C:\Documents and Settings\<user name>\Local Settings\Temp
- Use the DAS Menu - turns on log just for the current
session.
- After you run DAS, select Help | Turn on Log
- Use Help | Open Log to view the contents of the log.
DAS Trace is available in version 4.0. The DAS Trace can be useful
to see DAS's execution milestones. To turn on the Trace:
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\ReportsNow
- Add a new string value named: Trace
- Set Trace equal to 1
Back to Top
As of Windows XP SP2, Microsoft has disabled .chm content across the
network. Please see this Knowledge Base article on how to fix:
http://support.microsoft.com/kb/892675/
Back to Top
DAS signs all executables with a Digital Certificate that ReportsNow created. This ensures that all executable files cannot be
tampered with. Because ReportsNow is not a Root Certificate
authority, IE7 now issues this warning message when you run DAS. You
can alter the security settings per the KB article below to fix this issue.
Please apply "Method 2" to avoid the Navigation Blocked window below...
http://support.microsoft.com/default.aspx?scid=kb;en-us;931850
Back to Top
DAS enforces EnterpriseOne row and column security as follows:
- If a user is unauthorized to view an EnterpriseOne column, DAS:
- Does not load data for that column.
- Prevents the user from showing that column.
- If a user is unauthorized to view an EnterpriseOne row (based on E1
row security), DAS:
- Does not return that row to the grid.
Back to Top
Yes. DAS provides a security system that allows the administrator
to:
- Secure DAS functionality from specific E1 users or groups
- Secure which tables a user or group may open.
The security system is based on a hierarchical model that simplifies
security maintenance.
Back to Top
Use DAS.exe if this is the first time you are installing Data Access
Studio to a deployment server. Use DASUpdate.exe when you apply
subsequent Data Access Studio update versions to your deployment server.
DAS.exe contains the following deliverable files:
- DAS.MSI
- DAS_EULA.htm
- Setup.exe
- dotnetfx.exe
- InstMsiW.exe
- MDAC_TYP.exe
DASUpdate.exe contains the following deliverable files:
- DAS.MSI
- DAS_EULA.htm
- Setup.exe
As you can see, the difference between DASUpdate.exe and DAS.exe is the
following files:
- dotnetfx.exe
- InstMsiW.exe
- MDAC_TYP.exe
The above files are Microsoft redistributables that are the
pre-requisites for running DAS. Once you have run DAS.exe, then the
pre-requisites are installed and do not need to be installed again.
From this point on you may take the smaller download that is DASUpdate.exe
Other than the prerequisite files, DAS.exe and DASUpdate.exe do the
same thing. For the remainder of the FAQ, we will refer to the
installation executable as DAS.exe.
Back to Top
DAS.exe and DASUpdate.exe read information from your EnterpriseOne
system to determine how to install Data Access Studio. Because of
this requirement, the DAS.exe installer prompts you with an EnterpriseOne
sign in. Once you sign in, the DAS.exe installer reads information,
such as the location of the deployment server, to determine what needs to
be installed where.
The instructions DO NOT recommend that you run DAS.exe on your
deployment server for the following reasons:
- The deployment server is a central part of the E1 system. The
less you execute on the deployment server the better. By running
from a workstation instead of the deployment server, you know that the
only way the deployment server is impacted is that the installer creates
a new directory and copies files to it.
- The DAS.exe requires the .NET framework to run. This means
that you will be prompted to install the .NET framework prior to running
DAS.exe. Although it should be perfectly fine, you may not want to
install the .NET framework on your deployment server.
- The deployment server has a bootstrap environment called PLANNER
that will not work with the installer. You may be tempted to
select PLANNER if you run DAS.exe on the deployment server. If
install from a workstation, on the other hand, the PDXXXX, DVXXX, and
PXXXX environments are all valid environments for the DAS installer.
Back to Top
DAS.exe creates a directory called "Data Access Studio" on your
deployment server to support the following:
- Common EnterpriseOne share. All E1 workstations have access to the E1 share on the deployment
server. This means that E1 workstations will be able to run "Data
Access Studio\Setup.exe" to install the DAS client.
- EnterpriseOne standards. Data Access Studio integrates tightly with E1. The deployment
server's role in E1 is to be the central location for installation
(E.g., OneWorld Client Install). The Data Access Studio setup
program (setup.exe and DAS.msi), therefore, should be placed on this
server.
- Automatic DAS client update. The deployment server
directory holds the current version of DAS for auto update. If you
deployed the DAS full client solution to your enterprise, then when each
user runs DAS, the DAS client queries this directory for the DAS
version. If you apply a DAS update, then this directory will have
a newer version that the DAS client. The DAS client will detect
this and automatically update itself with the newest version.
Back to Top
Yes -- although this configuration is not recommended (see
Why
does DAS.exe create a directory on my deployment server)
When you run DAS.exe on a workstation, and you get to the "Target
Folder" Wizard screen, enter a local folder (such as C:\DAS) instead of
the Deployment Server folder that the installer provides. This will then
extract the DAS install components to the selected local folder. After
DAS.exe is complete, share the local folder (i.e.
C:\DAS) so that other workstations can install DAS by running
C:\DAS\Setup.exe.
This procedure will not update the deployment server. However, this
procedure will still create one table FDASPROP in your system datasource and
one OCM mapping.
Back to Top
FDASPROP is the main storage table for Data Access Studio. This
table is where DAS stores layouts, reports, preferences, etc.
DAS.exe creates this table in the system datasource to ensure DAS users
have access to FDASPROP no matter which environment they sign in to.
Furthermore, because there is only one FDASPROP for your entire
enterprise, you DO NOT have to worry about environment promotion (e.g., DV->PY->PD).
After DAS.exe creates FDASPROP, it then creates an OCM mapping for
FDASPROP. This way, DAS will always know where the FDASPROP is
located regardless of the signed-in environment.
Note also, that because FDASPROP is a central table, users will have
their information stored consistently no matter how they run DAS, from
either
- Full client
- Citrix client
- DAS LAN server
- DAS Web server
The result of this configuration is easier maintenance and less hassle
for the users and system administrators.
Back to Top
You may deploy DAS to your enterprise in any of three ways:
- Workstation
- Citrix
- DAS LAN Server
- DAS Web Server
In the Workstation deployment, your users already have a E1 full client
install. Your users install the DAS client to their workstations.
Once installed, DAS runs entirely from the user's workstation -- consuming
resources only from the workstation and the database.
In Citrix deployment, your users do not have an E1 full client install
and are typically located on a WAN. Once installed and published on
Citrix, your users dial in to the Citrix server and run DAS. DAS
consumes resources from the Citrix server and database.
In the DAS LAN your users do not have an E1 full client install
and are located inside your LAN. Once installed, user's run DAS from
a shared link. DAS consumes resources on the DAS LAN server, the
user's workstation, and the database.
In the DAS Web Server, your users are located in a Wide Area Network.
Users run DAS from a web page link (hosted by IIS, Apache or other
suitable web server). DAS consumes resources on the DAS LAN server,
the user's workstation, and the database.
Back to Top
For workstations and Citrix Servers that have DAS installed, use
Add/Remove programs. Remove Data Access Studio.
For the deployment server, delete directory: \Data Access Studio
For FDASPROP, use the drop table command to drop the table from the
database.
If you set up a DAS Web Server or DAS LAN Server, you need to uninstall
the Data Access Studio Service as follows:
installUtil.exe /uninstall DASServer.exe
Back to Top
When you upgrade EnterpriseOne, you will need to do the following:
- Sign on to your existing DAS instance with user DASADMIN (for more
information about DASADMIN consult the DAS help guide.)
- Click File | Work with DAS Instance...
- Click the "Export" button. On the Export DAS Instance file dialog,
click Save. Data Access Studio will export the DAS Instance data to the
.dasi file you specified. You will use this .dasi file in the next step to
import to the new instance.
- Download the latest DAS.exe from
Downloads.
- Follow the "Deployment Server Install instructions" to Install Data
Access Studio to your new EnterpriseOne instance (this will create the
FDASPPROP table in the new instance's system datasource.)
- On your new E1 instance, sign into DAS with user DASADMIN.
- Click File | Work with DAS Instance...
- Click the Import tab and click the "Import" button.
- On the Import DAS Instance file dialog, select the .dasi file and
click Open.
Data Access Studio will proceed to import the contents for the .dasi
file into your new instance. This procedure will work across
non-Unicode to Unicode upgrades as well. For more information,
please consult the DAS
Help Guide under the section Upgrading EnterpriseOne.
Back to Top
If the workstation with the behavior is a fat client:
1. In Windows, click Start | Run
2. Type:
regsvr32 "C:\Program
Files\ReportsNow\Data Access Studio\dsoframer.ocx"
(You may need to change the path to your actual Data Access Studio
directory)
If the workstation is a thin or web client:
1. In Windows, click Start Run:
2. Type: regsvr32 "\\<WebServerName>\DASBin\dsoframer.ocx"
(You will need to substitute the name of your DAS Web server for <WebServerName>
in the command above.
Back to Top
Delete Excel11.xlb file located at C:\Documents and
Settings\<username>\Application Data\Microsoft\Excel.
Back to Top
|
