JP2012053600A - File management device, control method of file management device, program, and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a file management device which is capable of restricting unintentional updating of an electronic file registered by using link information.SOLUTION: The file management device includes: link file designation means which designates an electronic file linked in association with data displayed in a screen; link setting means which sets the electronic file designated by the link file designation means, as a link; and attribute restricting means which imposes restrictions on attributes relating to the access right to the electronic file set as the link by the link setting means.

Description

  The present invention relates to a file management apparatus that manages an electronic file managed in association with a matter such as an electronic form.

2. Description of the Related Art Conventionally, an inquiry management system and a case management system that manage inquiry contents by using electronic forms and manage cases have been used. In addition, a related document file can be registered in the electronic form, and the electronic file can be shared by a plurality of client devices or users.
As a method of association, there are mainly a method of attaching a file and a method of registering link information to the file.
In the case of a method for attaching a file, since the system manages the attached file, the corresponding document file is not manipulated.

  On the other hand, as a method of registering link information to a file, there is a method as described in Patent Document 1. Here, a file management method for managing a shared file by a plurality of client devices is disclosed, and the server device and the client device are switched and stored as a destination for storing the substance of the shared file.

JP 2009-230583 A

  However, even if the storage destination of the shared file is a server device or a client device, the operating system can access the shared file.

  As a result, the shared document file may be overwritten, deleted, or moved despite being registered in association with the electronic form. In this case, if the related document file cannot be opened (eg moved) from the electronic form, or if it is overwritten even if it is opened, the contents may be different from the document file at the time of registration. There was a problem such as.

  In view of the above problems, an object of the present invention is to provide a file management apparatus capable of restricting unintended updates to an electronic file registered using link information to a file.

  Link file specifying means for specifying an electronic file to be linked in association with data displayed on the screen, link setting means for setting the electronic file specified by the link file specifying means as a link, and link setting by the link setting means Attribute limiting means for limiting an attribute relating to the access right to the electronic file.

  According to the present invention, an unintended update can be restricted for a document file registered using link information to the file.

1 is a system configuration diagram of a document management system in an embodiment of the present invention. FIG. It is a hardware block diagram of the information processing apparatus which can apply the file management apparatus in embodiment of this invention. FIG. 3 is a software configuration diagram of an information processing apparatus to which the file management apparatus in the embodiment of the present invention can be applied. It is a figure which shows an example of the login screen of the inquiry management system in embodiment of this invention. It is a figure which shows an example of the bulletin board in the inquiry management system in embodiment of this invention. It is a figure which shows an example of the applicable person narrowing-down search screen in the inquiry management system in embodiment of this invention. It is a figure which shows an example of the inquiry log | history screen in embodiment of this invention. It is a figure which shows an example of the inquiry management information CSV output screen in embodiment of this invention. It is a figure which shows an example of the inquiry reference screen (impossible correction) in embodiment of this invention. It is a figure which shows an example of the inquiry input screen in embodiment of this invention. It is a figure which shows an example of the screen which opens the file in embodiment of this invention. It is a figure which shows an example of the inquiry input screen in embodiment of this invention. It is a figure which shows an example of the whole flow at the time of file operation in embodiment of this invention. It is a flowchart which shows an example of the "reference" process in embodiment of this invention. It is a flowchart which shows an example of the "deletion" process in embodiment of this invention. It is a flowchart which shows an example of the 1st "open" process in embodiment of this invention. It is a flowchart which shows an example of the 2nd "open" process in embodiment of this invention. It is a figure which shows an example of the inquiry management table in embodiment of this invention. It is a figure which shows an example of the user management master and subscriber management master in embodiment of this invention. It is a figure which shows an example of the information regarding the file attribute in embodiment of this invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a system configuration diagram of a document management system according to an embodiment of the present invention.

  As a document management system, a file management apparatus 101, a server apparatus 102, a user terminal 103, and a printing apparatus 104 are connected via a communication network 150 in a communicable state. In this embodiment, as an example to which the document management system can be applied, it will be described as an inquiry management system for employee pension or corporate pension. However, the present invention is not limited to this, and document management that manages electronic files associated with electronic forms is possible. It is also applicable to the system.

  The file management apparatus 101 is a terminal in which a person in charge who receives an inquiry from a customer inputs the contents into an electronic form. At that time, if there is an electronic file related to the input content, it is stored in association with the electronic form. As a storage destination, a local disk of the file management apparatus 101 or a storage area of the server apparatus 102 can be used. Even when the file is stored in the local disk of the file management apparatus 101, the local disk can be set so that it can be shared so that it can be referred to from other terminals.

  The server apparatus 102 is used as a shared area when a person in charge of operating the file management apparatus 101 saves an electronic file. It is also possible to configure the server apparatus to have the functions of the file management apparatus 101.

The user terminal is a user terminal of the inquiry management system, and can refer to the electronic form registered by the file management apparatus 101. In addition, the user terminal 103 can have the function of the file management apparatus 101.
The printing apparatus 104 is used to print the contents of electronic forms and other information in the document management system.
FIG. 2 is a hardware configuration diagram of an information processing apparatus to which the file management apparatus according to the embodiment of the present invention can be applied.
Based on the program stored in the program ROM 203, each device connected to the system bus 200 is controlled to control the entire information processing apparatus.
The data ROM 204 stores various data. A RAM 202 functions as a main memory, work area, and the like for the CPU 201.

A keyboard controller (KBC) 205 controls input from a keyboard (KB) 209 or a pointing device (not shown) such as a mouse. A display controller (DC) 206 controls display on the display 210. The display may be a CRT or another type of display device such as an LCD.
A memory controller (MC) 207 controls access to the hard disk (HD) 211.
A peripheral device connection interface (USB I / F) 208 controls access to a portable storage medium (not shown) and other peripheral devices.
A network interface (NW I / F) 220 controls communication with the output device 230 via the network 150.

FIG. 3 is a software configuration diagram of an information processing apparatus to which the file management apparatus according to the embodiment of the present invention can be applied. The hardware configuration such as the CPU 201 in FIG. 2 is a software configuration that functions by operating in cooperation with each other.
Various databases can be stored in the file management apparatus 101 hard disk.

Various databases include a subscriber master 311, a user management master 312, and an inquiry management table 313. It is possible to have other databases as needed. Further, it can be stored in the hard disk of the server apparatus 102.
The subscriber master 311 is master data of subscribers to the welfare pension or the corporate pension, and a user who makes an inquiry is registered.

  The user management master 312 is master data of a user who uses the inquiry management system in this embodiment, and a user who inputs an inquiry received from a subscriber to the inquiry management system is registered.

  In the inquiry management table 313, inquiry data input from a user of the system is registered in the inquiry management system according to this embodiment. Information on the link file registered in relation to the inquiry content is also registered in the inquiry management table.

  The software function includes a subscriber data acquisition unit 301, an inquiry data acquisition unit 302, a link file determination unit 303, and a link file operation unit 304.

  The subscriber data acquisition unit 301 acquires subscriber data from the subscriber master 311. The inquiry data acquisition unit 302 acquires inquiry data from the inquiry management table 313. The link file determination unit 303 determines whether or not a link file is associated with the inquiry data. The link file operation unit 304 operates an attribute including the access right of the link file associated with the inquiry data.

FIG. 4 is a diagram showing an example of a login screen of the inquiry management system in the embodiment of the present invention. Information about the system user is stored in the user management master 312.
The top menu 410 of the inquiry management system includes an inquiry management processing menu 420 and a maintenance menu 430.

The inquiry management processing menu 420 includes an inquiry management menu 421 for inputting and referring to inquiry contents, an inquiry CSV output menu 422 for outputting inquiry contents in CSV, and a bulletin board menu 423.
The bulletin board is displayed when the bulletin board menu 423 is pressed, but may be configured to be automatically displayed when the system is started.

The maintenance menu 430 includes a user management master maintenance menu 431 and an inquiry classification master maintenance menu 432. In the user management master maintenance menu 431, maintenance of the user management master 312 can be performed. In the query category master maintenance, various category masters used in the query management table 313 can be maintained.
FIG. 5 is a diagram showing an example of a bulletin board in the inquiry management system according to the embodiment of the present invention.
The bulletin board 500 has a bulletin area 501 in which known items from the system administrator to the system user are displayed.
Returning to the description of FIG. When the inquiry management menu 421 is selected, an appropriate person narrowing search screen 600 shown in FIG. 6 is displayed.
FIG. 6 is a diagram showing an example of a relevant person narrowing search screen in the inquiry management system according to the embodiment of the present invention.

  In this inquiry management system, first, it is specified which subscriber the inquiry is from. After that, it is possible to refer to past inquiry contents from the inquiry history from the specified (corresponding) subscriber, or to register newly received inquiry contents.

  In the applicable person narrowing search screen 600, a subscriber number 601, a beneficiary number 602, a basic pension number 603, and an employee number 604 can be specified as search targets. A search is performed by pressing a radio button in front of each item and inputting a keyword (number) to be searched in a search box arranged on the right side.

  As other search methods, it is also possible to search by specifying a subscriber's name 605, name Kana 606, date of birth 607, and the like. Searching is performed by inputting a keyword to be searched in a search box arranged on the right side of each item.

  The relevant person narrowing search screen 610 is a diagram showing an image in which “% Kannon%” is entered in the search box of the name field 605 and the search result is displayed. This search is executed by searching the subscriber master 311 for subscribers whose “name” includes “Kannon”.

As the search results, the subscriber number 611, the recipient right number 612, the name 613, the name kana 614, the gender 615, the date of birth 616, and the like are displayed from the contents stored in the subscriber master. Here, by selecting and double-clicking on the line registered as the subscriber number 110012377, the details of the inquiry history of the corresponding line are displayed.
FIG. 7 is a diagram showing an example of an inquiry history screen in the embodiment of the present invention.
In the inquiry history screen 700, the inquiry history of the subscriber number 110012377 “Taro Kannon” selected in FIG. 6 is displayed.
Specifically, a response start date 701, a progress category 702, an inquiry category 703, details 704, a response 705, and the like are displayed.

The response start date 701 displays the date on which the response to the inquiry has started. In the progress category 702 and the inquiry category 703, categories set in the inquiry management system are displayed. The details 704 and the response 705 display the response performed by the operator (system user) who received the inquiry, and display what is input by the operator.
When the inquiry CSV output menu 422 is selected in FIG. 4, an inquiry management information CSV output screen 800 shown in FIG. 8 is displayed.
FIG. 8 is a diagram showing an example of the inquiry management information CSV output screen in the embodiment of the present invention.

On the inquiry management information CSV output screen 800, CSV output of the data in the specified output range and screen confirmation can be performed. When the query category 801 having “01 year price query” is selected and the search is executed, the search result display field 803 displays the search results whose query category is the annual price query.
By specifying and executing an output destination file in the CSV output destination column 802, it is possible to output as a CSV file.
In addition, an inquiry reference screen (uncorrectable) 900 is displayed by double-clicking an item for which inquiry contents are to be referred to, for example, the line displayed at the top.
FIG. 9 is a diagram showing an example of an inquiry reference screen (uncorrectable) in the embodiment of the present invention.

  The inquiry reference (cannot be modified) screen 900 can refer to the details of the inquiry content, but since it is called from the inquiry management information CSV output screen 800, the content cannot be corrected. Here, what is called attachment is a name on the screen, and in the present embodiment, by actually registering link information to the electronic file to be associated, the electronic file is associated with the matter using the attachment menu. Registered.

The link file is also grayed out so that the attachment field 901 cannot be operated. However, if the link file is opened by pressing the open button 902, the file attribute is managed by the operating system, so that it may be edited. Therefore, in the present invention, when the link file is opened from the inquiry reference screen that cannot be modified, it is possible to control the writing so that no matter what the attribute of the link file is. Yes. Details will be described later.
FIG. 10 is a diagram showing an example of an inquiry input screen according to the embodiment of the present invention.

The inquiry input screen 1000 is displayed by double-clicking an item to be referred to from the search result of the inquiry history screen 700 of FIG. 7, for example, a detail line displayed at the top. The screen is also displayed by pressing a new button in FIG. In that case, it is displayed in a state where nothing is entered.
Here, a description will be given assuming that the same screen as the inquiry reference (uncorrectable) screen 900 in FIG. 9 is displayed.

When it is desired to set a link file as an attached file to the displayed case, a file is selected on the file selection screen 1100 displayed by pressing the reference button 1002. When a file is selected, a check is added to the attachment field 1001.
An operation can be performed by pressing each button such as update 1003, delete 1004, and cancel 1005 for an open case.
FIG. 11 is a diagram illustrating an example of a file opening screen according to the embodiment of the present invention.

This is displayed when the reference button 1002 in FIG. 10 is pressed. When a file is selected in the file selection field 1101, the selected file is displayed in the file name field 1102, and by pressing an open button 1103, the corresponding file is selected as a link file. The file displayed here may be displayed with only the file name or the file path. When a file is selected and specified, a state like a query input screen 1200 shown in FIG. 12 is obtained.
FIG. 12 is a diagram showing an example of an inquiry input screen in the embodiment of the present invention.

  The inquiry input screen 1200 shows a state after a link file is selected as an attached file from the inquiry input screen 1000 of FIG. The attachment column 1201 is checked and an open button 1202 is displayed. When this open button is pressed, the link file is opened. In the inquiry input screen 1000 of FIG. 10, it is displayed as a reference button 1002.

Here, it is a file selected and specified as a link file, but since the path to the file is registered as link information, there are cases where the file is changed or deleted. . In order to prevent this, in the present embodiment, when a file is selected and specified as a link file, the file attribute is changed to write prohibition or movement prohibition.
Details will be described with reference to the flowcharts of FIGS.
FIG. 13 is a diagram showing an example of the overall flow at the time of file operation in the embodiment of the present invention.
The process starts when a process related to file operation is selected from the inquiry reference (cannot be modified) screen 900 or the inquiry input screens 1000 and 1200.

  A file operation is accepted in step S1301, and the operation type is determined in step S1302. If the file operation is “reference”, the process proceeds to “reference” processing in step S1303. If the file operation is “delete”, the process proceeds to “delete” processing in step S1304. If the file operation is “open”, the process proceeds to “open” processing in step S1305, and the processing ends.

“Delete” in the file operation indicates that the attachment column 1201 is unchecked. “Reference” is determined when the reference button 1002 is pressed, and “Open” is determined when the open button 902 or 1202 is pressed.
FIG. 14 is a flowchart showing an example of the “reference” process in the embodiment of the present invention.

  In step S1401, a file selection screen 1100 is displayed. In step S1402, it is determined whether a file has been determined. If it is determined that a file has not been determined, the process ends. On the other hand, if a file is selected, a link is set in step S1403. Specifically, the link file information is written in the inquiry management table 313. As a result, the link file is registered in association with the data (case) displayed on the inquiry input screen.

The associated data may be an electronic form screen as in the present embodiment, an html format document, or an application document such as a workflow format, and a path for accessing the associated electronic file is designated. Applicable if possible. Details of the inquiry management table will be described later.
In step S1404, a check is added to the attachment field. This check is also used when deleting links to files.

  In step S1405, the file attribute information is updated. Specifically, the attribute of the corresponding file is set to “write prohibition” and “deletion prohibition”. Both may be prohibited, or only one of them may be prohibited. It is also possible to set any attribute that can be set by the file system. Then, the file attribute table 314 is updated. Details of the file attributes will be described later.

In step S1406, the button name is changed. Specifically, the “Open” button is set when the link file is set, and the “Browse” button is set when the link file is not set (that is, the link can be set in the future). finish.
FIG. 15 is a flowchart showing an example of the “deletion” process in the embodiment of the present invention.
In step S1501, the link is deleted. Specifically, the information regarding the link file is deleted from the inquiry management table.
In step S1502, a process of removing the check given to the attachment column is performed.

In step S1503, the file attribute information is updated and the process ends. The update of the attribute information of the file indicates that the update information is registered in the file attribute table after restoring the attribute of the link file. Here, “return” refers to returning the attribute of the file changed by the “attachment” process to the state before being changed. The state before the change is stored in the file attribute management table.
FIG. 16 is a flowchart illustrating an example of a first “open” process according to the embodiment of this invention.

When the open button is pressed from the inquiry input screen 1200, the attribute of the link file should be restricted. In view of this, it is a flowchart in a case where a user who has set a link file by this system can perform updating.
In step S1601, file attribute information is acquired from the attribute management table 314.

  In step S1602, for example, it is confirmed whether the attribute is write-protected. If it is not write-protected, the process proceeds to step S1605, and the file is opened with the same attribute (not write-protected).

  On the other hand, if writing is prohibited, it is determined in step S1603 whether the user who is the current operator is the owner of the matter. If the user has administrator authority or if a case is registered, it is determined that the user is the owner.

If it is determined in step S1603 that the user is not the owner, the file is opened with the same attribute (write prohibition) in step S1605. On the other hand, if it is determined that the user is the owner, the file attribute information is changed in step S1604, the file is opened in a state where writing is not prohibited in step S1605, and the process ends.
Thereby, even if the attribute of the link file is restricted, the link file can be updated even if the operator is the owner.
FIG. 17 is a flowchart illustrating an example of a second “open” process according to the embodiment of this invention.

  In the first “open” process, even if the attribute of the link file is limited, the owner can update the file. However, when an attached file is opened from FIG. 9 and the inquiry reference screen that cannot be modified, it is desirable that the file cannot be updated even by the owner. FIG. 17 shows an embodiment corresponding to this.

  In step S1701, the attribute of the link file is acquired. In step S1702, it is determined whether writing is prohibited. If it is write-protected, the process advances to step S1705 to open the file with the same attribute (write-protected).

  On the other hand, if writing is not prohibited, it is determined in step S1703 whether the matter is opened from the reference screen. If it is not opened from the reference screen, the file is opened with the same attributes (not write-protected). This case applies to the case where the user is the owner in FIG.

  If the access is from the reference screen in step S1703, the file attribute information is changed, and the link file is opened in a write-protected state in step S1705, and the process is terminated.

Thus, even when the link file is accessed from the reference screen (cannot be modified) and the attribute of the link file is not restricted, the file can be opened with writing prohibited, and an erroneous operation or the like can be prevented.
FIG. 18 is a diagram showing an example of an inquiry management table in the embodiment of the present invention.
In the inquiry management table 1800, details of inquiry contents are recorded for all cases. Information registered from the inquiry input screen 1000 or the like is recorded.

Uniquely assigned reference number 1801, subscriber number 1802, case response start date 1803, response end date 1804, time required for response end 1804, inquiry category 1806, progress category 1807, comment details 1808, comment support 1810, updater 1811, link file 1, link file 2, registrant ID 1814, and the like are recorded.
These recorded contents are also used as search words when searching.

  The registrant ID column 1814 stores the ID of the user who registered the case, and the updater column 1811 stores the ID of the user who updated the case. If it is stored in either of these, it is the owner of the item.

The link file 1 column 1812 and the link file 2 column 1813 store files registered as link files as attachments from the inquiry input screen 1000 or the like. When a link is deleted, it is deleted from this column. Further, the number of link files is not limited to two, and a larger number can be managed.
FIG. 19 is a diagram illustrating an example of a user management master and a subscriber administrator master in the embodiment of the present invention.

The user management master 1900 stores a user ID 1901, a person in charge name 1902, a password 1903, an administrator authority 1904, a user registration date 1905, a change date 1906, an update user 1907, and the like.
The system user who uses the system needs to be registered in this user management master.

The subscriber management master 1910 is master data of a subscriber to the welfare pension or pension fund in the embodiment of the present invention. A subscriber number 1911, a beneficiary number 1912, a company entry date 1913, a name 1914, a name Kana 1915, a gender 1916, a date of birth 1917, and the like are stored.
FIG. 20 is a diagram showing an example of information related to file attributes in the embodiment of the present invention.

  The property screen 2000 is an image diagram when the property screen of the file linked to the present system is opened. A file name is displayed in the file name 2001, and an attribute 2002 set for the file is described. As attributes, “write prohibition”, “hidden file”, and “deletion prohibition” are described as examples. However, the present invention is not limited to this, and any attribute provided by the system can be set.

  In the present embodiment, an attribute that is set as prohibited is expressed as an attribute being restricted. Also, canceling the prohibition setting is expressed as canceling the attribute restriction. That is, an attribute set as “write prohibition” or “deletion prohibition” is expressed as an attribute being restricted, and releasing the prohibition condition is releasing the attribute restriction. These restrictions are implemented by the link file operation unit 304.

The attached file attribute setting table 2010 records the past attribute and the current attribute set in the link file by the process in the attached field. For example, the current attribute of the attached file 2011 “c: ¥ temp.doc” is set to (1) write prohibition and (3) prohibition of deletion (since it is checked), and the attribute before the change is ( Indicates that none of (1) to (3) is set (because it is not checked). This is used to restore the attribute when the link file is deleted in the “delete” process of FIG.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  The program according to the present invention is a program that can be executed by a computer according to the processing method of the flowchart shown in the present invention. The program in the present invention may be a program for each processing method of each device.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by executing the reading.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

  As a recording medium for supplying the program, for example, flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk, solid state drive, or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention.
In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

201 CPU
202 RAM
203 Program ROM
204 Data ROM
205 KBC
206 DC
207 MC
208 UBS I / F
220 NW I / F

Claims (8)

A file management device capable of linking electronic files in association with data displayed on the screen,
Link file designating means for designating an electronic file to be linked in association with data displayed on the screen;
Link setting means for setting the electronic file specified by the link file specifying means as a link;
Attribute restriction means for restricting an attribute relating to an access right to the electronic file linked by the link setting means;
A file management apparatus comprising: Link file designation cancellation means for canceling the designation of the electronic file set as the link;
A link setting releasing means for releasing the link setting to the electronic file designated by the link file designation releasing means;
Attribute restriction releasing means for releasing the restriction on the attribute relating to the access right to the electronic file that has been unlinked by the link setting releasing means;
The file management apparatus according to claim 1, further comprising:   The file management apparatus according to claim 1 or 2, wherein the display of the link file designation unit is changed to a state in which the electronic file can be discriminated depending on whether the electronic file is linked or released. .   When the electronic file is accessed from link information on a screen displaying the data, the electronic file is opened in a state where the attribute restriction is released even if the attribute of the electronic file is restricted. The file management apparatus according to any one of 1 to 3. An attribute recording means for recording an attribute before the change of the attribute restricted by the attribute restriction means;
5. The file management apparatus according to claim 4, wherein the state in which the attribute restriction is released is a state in which an attribute before changing the attribute stored in the attribute recording unit is set. A control method of a file management apparatus capable of linking an electronic file in association with data displayed on a screen,
A link file designation step for designating an electronic file to be linked in association with the data displayed on the screen;
A link setting step for setting the electronic file specified in the link file specifying step as a link;
An attribute restriction step for restricting an attribute relating to the access right to the electronic file linked by the link setting step;
A method for controlling a file management apparatus, comprising: A program that causes a computer to function as a file management device that can link an electronic file in association with data displayed on a screen,
Link file designating means for designating an electronic file to be linked in association with data displayed on the screen;
Link setting means for setting the electronic file specified by the link file specifying means as a link;
Attribute restriction means for restricting an attribute relating to an access right to the electronic file linked by the link setting means;
A program for causing a file management apparatus to function.   A computer-readable storage medium storing the program according to claim 7.

Images