三菱電機 MX Sheet 軟體操作手冊

三菱電機 MX Sheet 軟體操作手冊

APPENDIX

APPENDIX

Appendix 1

Version Confirmation

This section explains how to confirm the MX Sheet version.

Confirm the MX Sheet version in the Product information about MX Sheet screen.

Screen display

[MX Sheet][Version Info.]

Appendix 2

Processing Speed of MX Sheet

This section explains the performance values and the scroll processing performance of Excel when the monitor and logging functions is executed using the personal computer of the following performance.

The performance values indicate the numbers of device points where no collection delay occurs when only one cell area is set to the Excel book and the device data of D device are collected by the monitor or logging function. (If multiple cell areas is set, reduce the number of device points per cell to maintain the same performance.)

The actual performance values vary depending on the performance or similar of the personal computer.

Use the performance values explained in this section as reference values.

Operating system

CPU : Pentium III(800MHz)

Memory

Excel

Cell area

: 256MB

R R

: Microsoft Excel 2002

: Only one

<Setting example 1>

The setting example 1 shows the case where only one access data is set.

A

<Setting example 2>

The setting example 2 shows the case where two or more access data are set.

143

(1) Performance values for Ethernet communication

The following table shows the performance values when the monitor and logging functions are executed using

Ethernet communication.

CPU type: Q25HCPU

Connected module: QJ71E71 (10Mbps)

Function

Monitor function 1s

Operation Interval

0.5s

Number of Device Points

Setting example 1 Setting example 2

4000points

*1

12000points

*1

800points

1792points

*1

5s

20000points

*1

10000points

*1

Logging function

1s

5s

5120points

*1

5120points

*1

1792points

*1

5120points

*1 : This number of device points applies to the case the data type is set to a character string.

*1

(2) Scroll processing performance of Excel

The following table shows the times required by Excel for scroll processing when the logging function is used.

The following times applies to the case only Excel is started on the personal computer.

Scroll Range

10 columns ¯ 1000 rows

10 columns ¯ 2000 rows

10 columns ¯ 65536 rows

256 columns ¯ 1000 rows

256 columns ¯ 2000 rows

256 columns ¯ 65536 rows

Time Required for Scroll Processing

0.95s

1.1s

6.1s

4.5s

6.8s

20min and 30s

144

APPENDIX

(3) File size at save and required time

The following table shows references for file size at save and time taken for saving a file depending on Excel version (Book format).

In Microsoft

®

Excel

®

2007 or later (especially in standard format), file size may increase or time taken for saving a file may lengthen.

Excel version

12 columns 30 rows

Size (MB)

Time

(second)

Cell range

128 columns 32768 rows 255 columns 65535 rows

Size (MB)

Time

(second)

Size (MB)

Time

(second)

Microsoft

®

Excel

®

2007

(standard format)

Microsoft

®

Excel

®

2007

(binary format)

Microsoft

®

Excel

®

2010

(standard format)

Microsoft

®

Excel

®

2010

(binary format)

0.034

0.022

0.035

0.022

Less than 1

Less than 1

Less than 1

Less than 1

11.1

0.45

11.1

0.46

7

3

4

2

42.5

14.3

42.5

14.3

23

11

14

8

Measurement condition: 1 type is set for cell settings (application: logging)

Measurement environment: Intel

®

Core™2 Duo E8400 3.0GHz, 1GB MM, Windows XP

®

Professional SP3

A

145

Appendix 3

Processing MX Sheet

This section explains the processing of MX Sheet.

Appendix 3.1

Collection delay and data dropout

On MX Sheet, collection delay, data dropout or similar problem may occur depending on the communication time with the programmable controller CPU and the collection timing of device data.

The following explains the collection delay and data dropout.

(1) Collection delay

Device data collection delay occurs depending on the communication time with the programmable controller CPU and the corresponding processing time.

Collection delay occurs only when "Operation time" is set to "Regular interval".

When a collection delay occurs, it is registered to the ErrorLog sheet as error information.

When a collection delay occurs, check the ErrorLog sheet.

The following explains the cases where a collection delay occurs.

(a) When the actual communication time is longer than the specified operation interval

When the communication time with the programmable controller CPU is longer than the operation interval of

MX Sheet, a device data collection delay occurs.

<Example>

"Operation time" is set to "Regular interval (3s)" but the communication time with the programmable controller

CPU is 5s

Operation interval set to 3s

3s

2s waiting time occurs.

Time

Communication time: 5s

Since communication time is longer, actual operation interval is 5s.

146

APPENDIX

(b) Collection delay when device trigger function is used

When the sum of the device trigger condition check time and the communication time with programmable controller CPU is longer than the operation interval of MX Sheet, a collection delay occurs during the next device trigger condition check.

<Example>

When "B0" = "When ON" is set as the device trigger condition (operation interval is 3s)

ON

B0

OFF

Operation interval set to 3s

3s

2s waiting time occurs.

Time

1)

2)

Time necessary for communication: 5s

1) Device trigger condition check time

2) Communication time

1) + 2) is time necessary for communication.

(c) Collection delay when handshake function is used

When the sum of the requesting device check time, the communication time with programmable controller CPU and the handshake processing time is longer than the operation interval of MX Sheet, a collection delay occurs during the next requesting device check.

<Example>

When the programmable controller CPU side requesting device is set to "M0" and the PC side responding device to "M100" (operation interval is 3s)

Operation interval set to 3s

3s

2s waiting time occurs.

Time

1)

2)

3)

Time necessary for communication: 5s

ON

M100

OFF

M0

ON

OFF

1) + 2) + 3) is time necessary for communication.

1) Requesting device check time

2) Communication time

3) Handshake processing time

A

147

148

(2) Data dropout

The data to be collected may dropout depending on the communication time with the programmable controller

CPU and the collection timing of device data.

The following explains the cases where a data dropout occurs.

(a) When the actual communication time is longer than the specified operation interval

When the communication time with the programmable controller CPU is longer than the operation interval, the data to be collected dropouts.

If a data dropout has occurred, increase the operation interval setting of MX Sheet.

<Example>

When "Operation time" is set to "Hourly (0min, 1min, 2min)" but the communication time with the programmable controller CPU is longer than 1min If previous data collection is still being executed when it is reached the operation time as shown below, a data dropout occurs on MX Sheet.

12:00 12:01 12:02

Time

Communication time: 1min 30s

Since data at 12:00 is being collected, data at

12:01 is not collected.

(b) Data dropout when device trigger function is used

condition cannot be checked and the data to be collected dropouts.

If a data dropout occurs during use of the device trigger, decrease the operation interval setting of MX Sheet.

<Example>

When "B0" = "When ON" is set as the device trigger condition (operation interval is 60s)

If the device trigger condition holds for the specified operation time as shown below, a data dropout occurs on

MX Sheet.

12:00

Device trigger condition is checked at every operation time.

12:01 12:02 12:03

Time

ON

B0

OFF

Data collection is executed when condition holds.

Condition has held but data collection is not executed since condition does not hold for condition check.

Remark

Note that if a data dropout occurs during use of the device trigger, error information is not displayed on the ErrorLog sheet.

APPENDIX

(c) Data dropout when handshake function is used

When the requesting device condition holds for the specified operation time, the data to be collected dropouts.

If a data dropout occurs during use of the handshake, decrease the operation interval setting of MX Sheet.

<Example>

When the programmable controller CPU side requesting device is set to "M0" and the PC side responding device to "M100" (operation interval is 60s)

If the requesting device condition holds for the operation time as shown below, a data dropout occurs on MX

Sheet.

12:00

Requesting device is checked at every operation time.

12:01 12:02 12:03

Time

A

ON

M100

OFF

ON

M0

OFF

Data collection is executed when requesting device condition holds.

Requesting device condition is held but data collection is not executed since condition does not hold for condition check.

Remark

Note that if a data dropout occurs during use of the handshake, error information is not displayed on the ErrorLog sheet.

149

(3) Data dropout when modem communication function is used

When modem communication function is used and "Telephone line connectivity time zone" is set for "Connect each time depending on the operation interval", a data dropout occurs due to use of a modem.

To collect the programmable controller CPU device data using modem communication function, set MX Sheet while considering the modem connection time.

If a data dropout occurs during modem communication, increase the operation interval setting of MX Sheet.

As operation interval, set time longer than sum of 1) + 2) + 3).

Operation interval

Time

1)

2)

3)

1) Time to connect to modem

2) Communication time

3) Time to disconnect from modem

Time necessary for modem communication

Appendix 3.2

Date and time

When the logging function and CSV logging are used, the date and time in the cell area and the CSV file may not be displayed correctly.

The following explains an example of the incorrect display, the causes and corrective actions.

<Example (when "Regular interval" is set to 1s)>

Although communication is made at the specified interval, the date and time are not displayed correctly as shown below, since the time when data is actually read exceeds the regular interval.

(Unlike with collection delay, the error information is not displayed in the ErrorLog sheet.)

Time of 20:41:08 is incorrectly displayed as 20:41:07.

<Causes>

• Multiple cell areas is set to the Excel book.

• Multiple cell areas use the same communication path.

• "Operation time" of the <<Operation Interval>> tab is set to "Regular interval".

<Corrective actions>

• Decrease the number of cells set to the Excel book.

• Increase the "Regular interval" setting.

• Reexamine the cell area settings. ( Page 151, Appendix 4.)

150

APPENDIX

Appendix 4

Creating the Excel spreadsheet for MX Sheet

When collecting/writing device data by using MX Sheet, the efficiency of communication with the programmable controller CPU varies depending on the cell area settings.

The following provides the example of setting cell area for more effective communication.

(1) Communication efficiency and cell area specifying method

When multiple cell areas is set, MX Sheet executes communication with the programmable controller CPU in order of the cell areas.

When the same communication path is set to multiple cell areas, communication efficiency decreases since all cell areas use one communication path to communicate with the programmable controller CPU.

The following setting example shows the case where the same communication path is set to multiple cell areas.

<Setting example>

A

(a) Inefficient setting

When the above setting example is divided into four cell areas as shown in the following table, MX Sheet executes communication four times. This causes communication load to increase, decreasing communication efficiency.

Cell area name

A

B

Product type

Lot No.

Cell area

C2

C3

C5: C7

E5: E7

Logical station number

Access data settings

Device setting

D0 Character string

0: Ethernet

D5 Character string

D10 16-bit integer

D20 16-bit integer

1

3

Number of cells

Operation

Interval

1s interval

(b) Efficient setting

When the above setting example is integrated into one cell area as shown in the following table, the collection/ write of device data is completed by performing communication once. This enables communication load to decrease, improving communication efficiency.

Cell area name Cell area

Product information C2, C3, C5:C7, E5:E7

Access data settings

Logical station number

Device setting

0: Ethernet

D0 Character string

D5 Character string

D10 16-bit integer

D20 16-bit integer

1

3

Number of cells

Operation

Interval

1s interval

151

(2) Communication efficiency and access data setting

When one type of device is set as multiple devices, the efficiency of communication with the programmable controller CPU decreases.

The following setting example shows the case where one type of device is specified consecutively.

<Setting example>

(a) Inefficient setting

If the above setting example is divided into three access data as shown below, MX Sheet recognizes them as three types of devices and executes communication, decreasing communication efficiency.

(b) Efficient setting

If the above setting example is integrated into one access data as shown below, MX Sheet recognizes it as one type of device and executes communication, improving communication efficiency

Remark

Any of the following settings prevents the improvement of communication efficiency even if efficient setting is set.

• When "Data Type" is set to "Bit", the device number setting of "Device" is not a multiple of 16.

• CN200 (current value of 32-bit counter device) or later of the FXCPU is set.

152

APPENDIX

(3) Communication efficiency and use of Excel function (cell reference)

When inconsecutive device data are displayed on Excel, the efficiency of communication with the programmable controller CPU decreases if multiple cell areas are set.

The following setting example shows the case where inconsecutive device data are displayed on Excel.

<Setting example>

A

(a) Inefficient setting

When the above setting example is divided into four cell areas as shown in the following table, MX Sheet executes communication four times. This causes communication load to increase, decreasing communication efficiency.

Cell area name

Line A

Line B

Line C

Line D

Cell area

C3: E3

C4: E4

C5: E5

C6: E6

Logical station number

Access data settings

Device setting

0: Ethernet

D0 Character string

D5 Character string

D10 16-bit integer

D15 16-bit integer

3

Number of cells

Operation

Interval

1s interval

(b) Efficient setting

When the above setting example is integrated into one cell area as shown in the following table and device data are collected in the other Excel spreadsheet (Sheet 2), this decreases communication load, improving communication efficiency.

Set cell reference so that Excel spreadsheet 1, which actually displays the device data, is refer to the corresponding cells within Excel spreadsheet 2, which collects the device data.

(MX Sheet need not be set in the Excel spreadsheet where device data is displayed actually (Sheet 1).)

Access data settings

Cell area name

Line information

Cell area

Logical station number

A2: E5 (Area set to Sheet 2) 0:Ethernet

Device setting

D0 16-bit integer

Number of

20

cells

Operation

Interval

1s interval

Sheet 1 (Excel spreadsheet where device data is displayed actually) Sheet 2 (Excel spreadsheet where device data is collected)

Set Sheet 1 to refer to cells of Sheet 2.

153

Appendix 5

Procedure to Transport Data to Other

Personal Computer

This section explains the procedure to transport the settings of MX Sheet from a development personal computer to an on-site personal computer.

MX Sheet and MX Component must be installed in the personal computer where the settings of MX Sheet is transported.

Start

*1

Start the communication setup utility and execute the export of the communication settings.

*2

Operation on development personal computer

Copy the following files to the on-site personal computer.

Excel book of MX Sheet

Export file of communication setup utility

Operation on on-site personal computer

Start the communication setup utility and import the export file created on the development personal computer.

*2

Start the Excel book of MX Sheet and recheck the settings.

Complete.

*1: The Excel book for MX Sheet should be created on

the development personal computer.

*2: For the import and export operations of communication

settings, refer to MX Component Version 4 Operating Manual.

154

APPENDIX

Appendix 6

HTML Files

This section explains the HTML file saved during MX Sheet operation.

(1) HTML file

MX Sheet allows an HTML file to be saved automatically into the folder specified when any of the following functions is used.

• Logging function (when cell is full)

• Alarm summary function (when cell is full)

• Automatic save setting

A

(2) Convenient use of HTML file

The data collected by MX Sheet can be snapshot-monitored from a business destination, office or other place via the Internet/intranet, with the plant side personal computer (personal computer where MX Sheet is operating) used as a Web server.

Web server

Plant

HTML file is created by automatic save function of MX Sheet.

Internet

Intranet

MX Sheet is unnecessary.

Plant conditions can be snapshot-monitored from office and business destination.

(3) Continuous operation when saving data automatically in HTML format

Do not operate MX Sheet continuously when the Automatic save function is set to save data in HTML format.

For operating MX Sheet continuously, exit and reactivate Excel periodically.

If data are saved repeatedly in HTML format with the Automatic save function,

Excel may not operate properly.

The time for allowable continuous operation differs according to the operating environment.

155

Appendix 7

Warning Messages on Windows

®

Appendix 7.1

Overview of warning messages

The user account control function is added to Windows Vista

®

or later.

By this function, a warning message is displayed when executing Excel with Administrator authority. (Page 151,

Appendix 4)

<Windows Vista ® >

<Windows ® 7 or later>

156

Appendix 7.2

Methods for disabling the warning messages

APPENDIX

● The user account control (UAC) function prevents a crash (e.g. prevention of startup of a program which executes unintended operation).

Before setting this function, grasp that the security function offered by UAC is disabled and fully understand the risk.

● Since UAC cannot be set to disable in Windows

®

8, the warning message cannot be disabled.

The following two methods are available for disabling a warning message.

(1) Disabling the user account control function

The following shows a procedure for disabling the user account control function.

(a) When using Windows Vista

®

Operating procedure

1.

Select [Start] [Control Panel].

A

2.

Select [User Accounts].

To the next page

157

From the previous page

3.

Select [User Accounts].

4.

Select [Turn User Account Control on or off].

5.

Clear [Use User Account Control (UAC) to help protect your computer] and click the button.

158

Complete

(b) When using Windows

®

7

Operating procedure

1.

Select [Start] [Control Panel].

APPENDIX

A

2.

Select [System and Security].

3.

Select [Change User Account Control settings].

To the next page

159

160

From the previous page

4.

Set the slide bar "Never notify" and click the

button.

Complete

(2) Allowing the warning message without showing it

The following shows a procedure for allowing a warning message without showing it.

1.

Select [Start] [Control Panel].

APPENDIX

A

2.

Select [System and Security].

When using Windows Vista

®

, select [Classic View].

3.

Select [Administrative Tools].

To the next page

161

162

From the previous page

4.

Select [Local Security Policy].

When user account control is enabled, the following screen is displayed.

Click the Continue button or the Yes button.

<Windows Vista

®

>

<Windows

®

7>

5.

Select [Local Policies].

6.

Select [Security Options].

7.

Select [User Account Control: Behavior of the elevation prompt for administrators in Admin

Approval Mode Prompt for consent].

8.

Select [Elevate without prompting] on the <<Local

Security Setting>> tab, and click the button.

Complete

APPENDIX

Appendix 8

Countermeasures for Errors as a Result of

Using the Automatic Communication Setting of MX Sheet in Microsoft

®

Excel

®

2007 or

Later

When a workbook that has been configured for "Automatic Communication Startup" using MX Sheet is opened using

Microsoft

®

Excel

®

2007 or later, the following anomalous situations may occur. (Page 114, CHAPTER 9)

Appendix 8.1

Situations

(1) Excel stops responding.

(2) One of the following error messages is displayed.

A

Appendix 8.2

Cause of anomalous situations

These situations may occur if the following conditions are met.

(1) An Excel book is opened after setting MX Sheet automatic communication startup.

(2) An Excel book is opened with Microsoft

®

Excel

®

2007 or later.

163

Appendix 8.3

Corrective action

Use the following flowchart to determine the course of action.

Start

Is Windows XP SP2 or earlier or

Windows Vista SP1 or earlier used?

...

Check the Service Pack for the operating environment.

Yes

Install the required Service Pack.

No

...

Page 165, (1) in this section

Check the .NET Framework and the related module not yet installed, and install it.

Execute "MXShRegRCom. exe".

Check that the action works.

Complete

...

...

...

Page 165, (2) in this section

Page 166, (3) in this section

Page 167, (4) in this section

Update MX Sheet or install Service Pack, .NET Framework, and the related module using the administrator account.

164

APPENDIX

(1) Installation of Service Pack

Install the Service Pack required for the used operating system.

For details of required service pack, refer to the following section.

Page 23, Section 2.1 Operating Environment

(2) Checking and installation of .NET Framework and the related module

The following tables list .NET Frameworks and the related modules required for each operating environment.

If they are not installed, install them in the order listed in the table.

The file is in the "DOTNET" folder.

(a) When using Windows XP

®

Excel version

Microsoft

®

Excel

®

2007

Microsoft

®

Excel

®

2010

.NET Framework and the related module

Microsoft

®

.NET Framework 3.5 SP1

Microsoft

®

.NET Framework 4.0 Extended

Microsoft

®

Visual Studio 2010

Tools for Office Runtime (x86)

Microsoft

®

.NET Framework 4.0 Extended

Microsoft

®

Visual Studio 2010

Tools for Office Runtime (x86)

File name on the CD-ROM

dotnetfx35.exe

dotNetFx40_Full_x86_x64.exe

vstor_redist.exe

dotNetFx40_Full_x86_x64.exe

vstor_redist.exe

(b) When using Windows Vista

®

Excel version

Microsoft

®

Excel

®

2007

Microsoft

®

Excel

®

2010

.NET Framework and the related module

Microsoft

®

.NET Framework 4.0 Extended

Microsoft

®

Visual Studio 2010

Tools for Office Runtime (x86)

(c) When using Windows

®

7

32-bit version

Excel version

Microsoft

®

Excel

®

2007

Microsoft

®

Excel

®

2010

Microsoft

®

Excel

®

2013

.NET Framework and the related module

Microsoft

®

.NET Framework 4.0 Extended

Microsoft

®

Visual Studio 2010

Tools for Office Runtime (x86)

 64-bit version

Excel version

Microsoft

®

Excel

®

2007

Microsoft

®

Excel

®

2010

Microsoft

®

Excel

®

2013

.NET Framework and the related module

Microsoft

®

.NET Framework 4.0 Extended

Microsoft

®

Visual Studio 2010

Tools for Office Runtime (x64)

File name on the CD-ROM

dotNetFx40_Full_x86_x64.exe

vstor_redist.exe

File name on the CD-ROM

dotNetFx40_Full_x86_x64.exe

vstor_redist.exe

File name on the CD-ROM

dotNetFx40_Full_x86_x64.exe

vstor_redist.exe

A

165

(d) When using Windows

®

8

*1

 32-bit version

Excel version

Microsoft

®

Excel

®

2007

Microsoft

®

Excel

®

2010

Microsoft

®

Excel

®

2013

.NET Framework and the related module

Microsoft

®

Visual Studio 2010

Tools for Office Runtime (x86)

File name on the CD-ROM

vstor_redist.exe

 64-bit version

Excel version

Microsoft

®

Excel

®

2007

Microsoft

®

Excel

®

2010

Microsoft

®

Excel

®

2013

.NET Framework and the related module

Microsoft

®

Visual Studio 2010

Tools for Office Runtime (x64)

File name on the CD-ROM

vstor_redist.exe

*1 : ".NET Framework 4.5 Advanced Services" needs to be enabled in "Turn Windows features on or off" on Control Panel.

Check if the required .NET Framework and the related module are installed or not by the following operations.

• When using Windows XP

®

Select [Start]  [Control Panel]  [Add or Remove Programs].

• When using Windows Vista

®

or later

Select [Start]  [Control Panel]  [Uninstall a program].

166

Check if the "Add or Remove Programs" screen or the "Uninstall or a change a program" screen displays the required .NET

Framework and the related module.

(3) Execution of "MXShRegRCom.exe"

After installing .NET Framework and the related module, execute "MXShRegRCom.exe" in the folder where MX

Sheet is installed ("C:\MELSEC\Sheet\" when the installation location folder was not changed at installation).

When the user account control is enabled, the following screen is displayed.

Click the button or the

<Windows Vista

®

>

button.

<Windows

®

7 or later>

The message shown in the figure to the left is displayed to notify the completion.

Click the button.

APPENDIX

(4) Checking if the action works

The following explains how to check if the action works or not.

1.

Start Excel.

2.

When either of the screens on the left is displayed,

click the button.

A

3.

Select the <<File>> tab [Options].

The Excel Options screen is displayed.

Select "Add- Ins", change the item in "Manage" to "COM

Add-ins", and click the button.

< When using Microsoft

®

Excel

®

2007 >

Select the office button

4.

"MXShRibbon" is displayed on the COM Add-Ins screen.

Check that "MXShRibbon" check box is selected.

Complete

167

Appendix 9

Differences with Previous Version of MX Sheet

(1) Comparison with MX Sheet Version 1

This section explains the differences between MX Sheet Version 2 and MX Sheet Version 1.

(a) Operating environment (Applicable software)

OS

*1

Excel

*1

MX Sheet Version 1

Microsoft

®

Windows

®

98

Microsoft

®

Windows

®

Millennium Edition

Microsoft

®

Windows

®

NT

®

Workstation

Microsoft

®

Windows

®

2000 Professional

Microsoft

®

Windows XP

®

Professional

Microsoft

®

Windows XP

®

Home Edition

Microsoft

®

Windows Vista

®

Home Basic

Microsoft

®

Windows Vista

®

Home Premium

Microsoft

®

Windows Vista

®

Business

Microsoft

®

Windows Vista

®

Ultimate

Microsoft

®

Windows Vista

®

Enterprise

Microsoft

®

Windows

®

7 Starter

Microsoft

®

Windows

®

7 Home Premium

Microsoft

®

Windows

®

7 Professional

Microsoft

®

Windows

®

7 Ultimate

Microsoft

®

Windows

®

7 Enterprise

Microsoft

®

Excel

®

2000 (English version)

Microsoft

®

Excel

®

2002 (English version)

Microsoft

®

Excel

®

2003 (English version)

Microsoft

®

Excel

®

2007 (English version)

Microsoft

®

Excel

®

2010 (English version)

*1 : Limitations on the supported Service Pack

MX Sheet Version 2

Microsoft

®

Windows XP

®

Professional

Microsoft

®

Windows XP

®

Home Edition

Microsoft

®

Windows Vista

®

Home Basic

Microsoft

®

Windows Vista

®

Home Premium

Microsoft

®

Windows Vista

®

Business

Microsoft

®

Windows Vista

®

Ultimate

Microsoft

®

Windows Vista

®

Enterprise

Microsoft

®

Windows

®

7 Starter

Microsoft

®

Windows

®

7 Home Premium

Microsoft

®

Windows

®

7 Professional

Microsoft

®

Windows

®

7 Ultimate

Microsoft

®

Windows

®

7 Enterprise

Microsoft

®

Windows

®

8

Microsoft

®

Windows

®

8 Pro

Microsoft

®

Windows

®

8 Enterprise

Microsoft

®

Excel

®

2003 (English version)

Microsoft

®

Excel

®

2007 (English version)

Microsoft

®

Excel

®

2010 (English version)

Microsoft

®

Excel

®

2013 (English version)

Remark

● Using the unsupported operating environment

Use MX Sheet Version 1 when using the operating environment which is not supported by MX Sheet Version 2.

MX Sheet Version 1 is included on the CD-ROM of MX Sheet Version 2.

● Details of operating environment

Refer to the following section and manual.

Page 23, Section 2.1 Operating Environment

MX Component Version 4 Operating Manual

The manual is included on the CD-ROM of MX Sheet Version 2 in a PDF file format.

(2) Compatibility

(a) Installation

MX Sheet Version 2 cannot be installed with MX Sheet Version 1.

Install MX Sheet Version 2 after uninstalling MX Sheet Version 1

(b) Utilizing Excel books

Excel books created in MX Sheet Version 1 can be used in MX Sheet Version 2 without modifications.

168

Memo

APPENDIX

A

169

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents