5 Reasons CEOs Prefer MV Dashboard Over Spreadsheets

5 Reasons CEOs Prefer MV Dashboards Over Spreadsheets

5 Reasons CEOs Prefer Executive MV Dashboard Over Spreadsheets:

1. Universal Platform: Visualize and combine data from your MultiValue Database.
2. Automated Reporting: Automatically update key metrics to gain insights in real time. No more waiting for reports.
3. Mobile Access: Spreadsheets are painful on your phone. With a dashboard, you can see your key metrics on any device.
4. Improve Performance: Real-time dashboards increase transparency and accountability, which help motivate your workforce.
5. Drill-Down Analysis: With the click of a mouse, executives can drill down into the exact data they want.

What Can an Executive MV Dashboard Do for Your Business?

If you’re like most CEOs, you’re working from multiple reports, trying to understand what’s happening in your business—and what to do about it.  While your brain may be sharp, it shouldn’t be the glue that holds this information together.  With MV Dashboard, you can see all the metrics that matter to you in a single, personalized CEO dashboard.

Because your data is often tucked away in many different corners of your MultiValue system, gathering and analyzing this information can be an inconvenient and time-consuming venture. You need a centralized, web-based portal that you can use daily to view critical stats about your business data and make real-time decisions. MultiValue Dashboard allows you to select and present your critical business data with intuitive, web-based graphical interfaces and widgets, giving you the tools you need to make rapid business decisions based on real-time data.

D3 Runtime-Errors File

Error Logging

This topic describes how to record compiling errors when using FlashBASIC. Errors encountered during runtime are logged to the DM,RUNTIME-ERRORS file. These errors can be displayed by using the TCL command LIST-RUNTIME-ERRORS

When compiling FlashBASIC programs with the o option, the compiler automatically logs all compilation errors if a data section called $log is present in the user's BASIC program file. The log is updated only when errors occur. Each log entry's ID is the same as the ID of the item being compiled.

The first attribute of the entry consists of the time and date that the error occurred as well as the phase of compilation where the error occurred. Other attributes can contain additional undefined information can contain UNIX error messages.

• Errors logged as phase 0 errors are problems detected by the standard FlashBASIC compiler.
• Errors logged as phase 1 and higher are FlashBASIC compilation errors.
• Errors occurring higher can indicate an installation problem or the lack of a resource, such as swap space. In these cases, attributes 2 and higher provide more exact error reporting.

For UNIX: Not supported

For Windows: FlashBASIC runtime errors can be logged to the Windows event log. This feature is set from the FlashBASIC tab of the D3 Device Manager (see the D3 System Administration Guide for more information).

A Windows event log entry has the following format:

Runtime error <err> @ <progname>:<lineno>

where:

<err>	FlashBASIC error message item-ID.
<progname>	Item-ID of the FlashBASIC module.
<lineno>	Source line number.

Additional information can also be logged in the Data section of the Windows event log (accessible through the Event Detail dialog box in the Windows event viewer). For example:

Runtime error B12 @ myprog:15

B12 is a file has not been opened error, occurring in module myprog at line 15.

Example(s)

To enable logging for a file called bp, type:

create-file bp,$log 7

Compiling using the o option now logs errors into the bp,$log file. These can be displayed by typing any of these commands:

ct bp,$log list-item bp,$log sort-item bp,$log