Method, System, and Apparatus for Providing Access to Workbook Models Through Remote Function Calls

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. Patent Application No. 10/306,937 filed November 26, 2002 and entitled "USER-DEFINED SPREADSHEET FUNCTIONS", which is expressly incorporated herein by reference.

BACKGROUND OF THE INVENTION

Much of the utility of a spreadsheet application program lies in the ability of a user to capture data and algorithmic operations in an organized structure, such as a worksheet (also referred to herein at a "spreadsheet"), without the need for professional computer programming capabilities. A non-programmer user can specify complex data relationships, including summing operations, amortization operations, and so on, without leaming a programming language. The non-programmer can utilize the capabilities of the spreadsheet application program in this manner to model complex numerical and financial relationships.

One of the problems with defining complex models within a spreadsheet application program is that the models are not encapsulated or labeled to support use by other users. In order to allow other users to access the model, it is typically necessary to employ the services of a programmer to code the model using a computer programming language. The compiled version of the model can then be published and utilized by other users. Coding a model in a programming language, however, requires the services of a skilled programmer and can therefore be very time consuming and expensive.

Alternatively, the workbook (a collection of worksheets or spreadsheets) containing the model may simply be shared with other users in a traditional manner, such as via a file share or through electronic mail. However, sharing a workbook containing a model in a traditional manner exposes the implementation of the model to each user that accesses the workbook. It may be desirable to hide the implementation of a model from the user, for instance, where the implementation of the model includes proprietary algorithms and calculations, but where it is still necessary to allow users to utilize the model. Current spreadsheet application programs do not provide a facility for allowing access to the model without permitting access to the underlying implementation.

It is with respect to these considerations and others that the various embodiments of the present invention have been made.

BRIEF SUMMARY OF THE INVENTION

In accordance with the present invention, the above and other problems are solved by a method, system, and apparatus for providing access to workbook models through remote function calls. Through the use of the embodiments of the invention, it is possible to share a workbook (a "workbook model" or "model") with other users without the need to code the model in a traditional programming language. Moreover, the workbook model is exposed for use without exposing the underlying implementation of the model.

According to one aspect of the invention, a system is provided for providing access to workbook models through remote function calls. According to one embodiment, the system includes a client computer capable of executing a spreadsheet application program for creating a workbook. The workbook may include one or more cells having data stored therein and may include application-provided or third-party pluggable functions used to define a model. Workbooks may also contain objects that bring data from external data sources (such as query tables or pivot tables) and may also contain calls to other workbook functions. Zero or more cells within the workbook may be defined as inputs to the model and one or more cells within the workbook may be defined as outputs from the model.

The spreadsheet application program may also be operative to receive a user request to make the workbook model available via one or more remote function calls. In response to such a request, the spreadsheet application program is operative to receive data from the user defining the new workbook function. In particular, the user may provide a name for the function and define the inputs, if any, and at least one output from the function. For instance, the user may identify the cells within the workbook that should be utilized as inputs to the function and provide a name for each input. Inputs may have default values and potentially be defined as optional (i.e. if they are not passed then the default is used). The user may also identify the cells within the workbook that should be utilized as outputs from the function and provide a name for each output. The user may also specify a server location at which the new workbook function should be published. Once the user has provided this data, the workbook and the data defining the function may be published to a server computer that is operative to receive and respond to remote function calls for the published workbook function.

The spreadsheet application program is further operative to call a remote workbook function from within the context of a workbook. The inputs to a remote function may be identified as cells within the workbook or parameters within a sub-formula. Once this information has been provided, the spreadsheet application program is operative to make a remote function call to the workbook function with the provided inputs. The remote function call may comprise a web services call made utilizing the simple object access protocol ("SOAP"). Other types of remote functions calls may also be utilized.

When a response is received at the spreadsheet application program from the remote function, the spreadsheet application program is further operative to receive the outputs from the function. The spreadsheet application program may place the outputs from the function into the cells within the workbook identified by the user for the function outputs or may utilize the outputs within a sub-formula. In this manner, a model may be defined within a workbook, published to a server computer, and called without exposing the underlying implementation of the model to the calling application.

According to aspects of the invention, the system also includes a server computer operative to execute a server program for receiving and responding to remote function calls directed toward workbook functions. In particular, the server computer is operative to receive and store workbooks and function definitions associated with the workbooks that define remote functions calls that may be made directed toward the workbook. The function definitions identify the name of the workbook function, a description of the parameters that should be used as inputs for the function, and a description of the parameters that should be used as outputs for the function. The server computer is also operative to expose the workbook functions so that the functions may be discovered by the clients that wish to make a remote call. Once the workbook functions have been exposed, client applications may discover and call the workbook functions through the use of remote function call.

When a call is received at the server computer for a workbook function, the server computer is operative to load the workbook. Once the workbook has been loaded, the server computer populates the cells in the workbook identified as inputs with input parameters received with the function call. If the workbook contains a reference to another data source, any data necessary to recalculate the workbook may be retrieved from the data source prior to the recalculation. References to other workbook functions may also be called. Once the workbook has been recalculated, the server computer is operative to retrieve from the workbook the contents of the cells defined as outputs for the function. The data contained in these cells is then returned as a reply to the remote function call. Any type of application that supports remote function calls may be utilized to call the workbook function on the server computer in this manner, including calls received from other server computers. It should be appreciated that a single computer may be utilized to perform the functionality of both the client and server computers as described herein.

The invention may be implemented as a computer process, a computing apparatus, or as an article of manufacture such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process.

These and various other features, as well as advantages, which characterize the present invention, will be apparent from a reading of the following detailed description and a review of the associated drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

<ul id="ul0001" list-style="none" compact="compact"><li>FIGURE 1 is a computer network diagram illustrating aspects of several computer systems utilized in and provided by the various embodiments of the invention;</li><li>FIGURE 2 is a computer system architecture diagram illustrating aspects of a client computer system utilized in and provided by the various embodiments of the invention;</li><li>FIGURE 3 is a flow diagram illustrating aspects of a process for publishing a workbook function to a server computer according to one embodiment of the invention;</li><li>FIGURE 4 is a screen diagram illustrating an aspect of the invention for providing a facility through which a user can define input and output cells for a workbook function according to one embodiment of the invention;</li><li>FIGURE 5A and 5B are flow diagrams illustrating aspects of processes for defining and calling a workbook function via web services according to one embodiment of the invention, respectively;</li><li>FIGURE 6 is a screen diagram illustrating an aspect of the invention for providing a facility through which a user can define the cells to be utilized as inputs and outputs when calling a workbook function via a remote function call;</li><li>FIGURE 7 is a flow diagram illustrating the steps performed by a server computer when receiving and responding to remote function calls for workbook models according to one embodiment of the invention; and</li><li>FIGURE 8 is a screen diagram illustrating the contents of a workbook following a call to a workbook function via a remote function call.</li></ul>

DETAILED DESCRIPTION OF THE INVENTION

Referring now to the drawings, in which like numerals represent like elements, various aspects of the present invention will be described. In particular, FIGURE 1 and the corresponding discussion are intended to provide a brief, general description of a suitable computing environment in which embodiments of the invention may be implemented. While the invention will be described in the general context of program modules that execute in conjunction with program modules that run on an operating system on a personal computer, those skilled in the art will recognize that the invention may also be implemented in combination with other types of computer systems and program modules.

Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

Referring now to FIGURE 1, an illustrative operating environment for the several embodiments of the invention will be described. As shown in FIGURE 1, a network 10 interconnects a client computer 2 and several server computers 12A-12C. It should be appreciated that the network 10 may comprise any type of computing network, including a local area network or a wide area network, such as the Internet. The network 10 provides a medium for enabling communication between the client computer 2, the server computers 12A-12C, and potentially other computer systems connected to or accessible through the network 10.

The client computer 2 comprises a general purpose desktop or laptop computer capable of executing one or more application programs. In particular, according to the various embodiments of the invention, the computer 2 is operative to execute a spreadsheet client application 4. As known to those skilled in the art, the spreadsheet client application program 4 provides functionality for creating budgets, performing financial forecasting, and other finance and numeric-related tasks. In order to provide this functionality, data values may be organized using cells and the relationships between the cells may be defined using formulas. A change to one cell produces changes to related cells. Spreadsheet programs usually provide graphing capabilities for output and a variety of formatting options for text, numeric values, and graph features.

According to embodiments of the invention, the spreadsheet client application 4 may be utilized to create a workbook 6. The workbook 6 is a file that is created by a spreadsheet program that contains one or more worksheets (a worksheet may also be referred to herein as a "spreadsheet"). A worksheet is a single page organized into rows and columns within the spreadsheet program and appearing on screen. Through the use of these features, a user can create models of financial and numerical problems and solutions. Additional details will be provided below as to how such workbook models may be published and then utilized through the use of remote function calls.

It should be appreciated that, according to one embodiment of the invention, the spreadsheet client application 4 comprises the EXCEL spreadsheet application program from MICROSOFT CORPORATION of Redmond, Washington. It should be appreciated, however, that the various aspects of the invention described herein may be utilized with other spreadsheet application programs from other manufacturers. Moreover, although the inventive aspects described herein are presented in the context of a spreadsheet application program, it should be appreciated that other types of application programs may also be utilized to embody the various aspects of the invention.

According to other embodiments of the invention, the client computer 2 may also be operative to execute a program 8 compatible with the simple object access protocol ("SOAP"). As will be described in greater detail below, workbook models may be published to the server computer 12A. The server computer 12A may then expose the workbook models to external callers through the use of remote function calls. For instance, through the use of web services, calls may be made to a workbook function exposing the workbook model. In one embodiment, the web service call may comprise a remote function call utilizing the SOAP protocol. The SOAP call may be made by the spreadsheet client application 4 or by the SOAP-compatible program 8. The SOAP-compatible program 8 may comprise any application or programming language capable of making a SOAP remote procedure call.

It should further be appreciated that in an alternative embodiment, the functions of the computer 2 described above may be divided among two computing devices. For instance, one computing device may be operative to execute the spreadsheet application 4 for publishing a workbook function while the other computing device may be operative to execute a client application, such as the SOAP-compatible program 8, for calling the workbook function. The client application may also be divided into one application that authors the workbook that calls the function and into another that actually performs the call. For example, the second one might be a server which runs the workbook that calls the workbook function.

The spreadsheet server application 13 comprises a server-based application program that may execute without the use of a display screen (headless). The spreadsheet server application 13 is operative to perform many of the functions of the spreadsheet client application 4 on a server computer. For instance, the spreadsheet server application 13 can load and calculate a workbook 6. As will be described herein, the spreadsheet server application 13 also provides functionality for receiving a workbook and data describing a workbook function. The spreadsheet server application 13 also exposes the workbook functions to outside callers and receives and responds to remote function calls. Additional details regarding the various functions performed by the spreadsheet client application 4 and the spreadsheet server application 13 will be provided below with respect to FIGURES 2-8.

Referring now to FIGURE 2, an illustrative computer architecture for a computer 2 utilized in the various embodiments of the invention will be described. The computer architecture shown in FIGURE 2 illustrates a conventional desktop or laptop computer, including a central processing unit 5 ("CPU"), a system memory 7, including a random access memory 9 ("RAM") and a read-only memory ("ROM") 11, and a system bus 12 that couples the memory to the CPU 5. A basic input/output system containing the basic routines that help to transfer information between elements within the computer, such as during startup, is stored in the ROM 11. The computer 2 further includes a mass storage device 24 for storing an operating system 18, application programs, and other program modules, which will be described in greater detail below.

The mass storage device 24 is connected to the CPU 5 through a mass storage controller (not shown) connected to the bus 12. The mass storage device 24 and its associated computer-readable media provide non-volatile storage for the computer 2. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available media that can be accessed by the computer 2.

By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks ("DVD"), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 2.

According to various embodiments of the invention, the computer 2 may operate in a networked environment using logical connections to remote computers through a network 10, such as the Internet. The computer 2 may connect to the network 10 through a network interface unit 20 connected to the bus 12. It should be appreciated that the network interface unit 20 may also be utilized to connect to other types of networks and remote computer systems. The computer 2 may also include an input/output controller 22 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in FIGURE 2). Similarly, an input/output controller 22 may provide output to a display screen, a printer, or other type of output device.

As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 24 and RAM 9 of the computer 2, including an operating system 18 suitable for controlling the operation of a networked personal computer, such as the WINDOWS XP operating system from MICROSOFT CORPORATION of Redmond, Washington. The mass storage device 24 and RAM 9 may also store one or more program modules. In particular, the mass storage device 24 and the RAM 9 may store a spreadsheet client application 4 and a SOAP-compatible program 8, as described above. The mass storage device 24 and RAM 9 may also store a workbook 6 created by the spreadsheet client application 4.

It should be appreciated that the server computers 12A-12C may include many of the conventional computing components illustrated in FIGURE 2 and described above. Additionally, the server computer 12A may be operative to store and execute a spreadsheet server application 13. The file server computer 12C may be operative to store and execute a file server application 28 for receiving and responding to requests for files stored in the repository 14, such as a workbook 6. It should be appreciated that the server computers 12A-12C may include other conventional components not illustrated in FIGURE 2 but known to those skilled in the art.

Referring now to FIGURE 3, an illustrative routine 300 will be described illustrating a process performed by the spreadsheet client application program 4 for publishing a workbook model to a server computer as a workbook function. When reading the discussion of the routines presented herein, it should be appreciated that the logical operations of various embodiments of the present invention are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance requirements of the computing system implementing the invention. Accordingly, the logical operations illustrated in FIGURES 3,5, and 7, and making up the embodiments of the present invention described herein are referred to variously as operations, structural devices, acts or modules. It will be recognized by one skilled in the art that these operations, structural devices, acts and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof without deviating from the spirit and scope of the present invention as recited within the claims set forth herein.

The routine 300 begins at operation 302, where a user utilizes the spreadsheet client application 4 to author the workbook 6. In particular, as described herein, the user may utilize the various facilities provided by the spreadsheet client application 4 to author a workbook containing a model. As defined herein, the term workbook model comprises a workbook authored in such a manner as to perform a numerical analysis and that includes one ore more cells that may be utilized as inputs for the model and one or more cells that provide the outputs from the model. The various functions and methodologies that may be utilized within a spreadsheet client application 4 to create a workbook model are virtually unlimited and well-known to those skilled in the art.

From operation 302, the routine 300 continues to operation 304, where the spreadsheet client application 4 determines whether a user has made a request to publish the workbook model to the server computer 12A as a workbook function. If the user has not made such a request, the routine 300 returns to operation 302 where the user may continue to author the model. If the user does request to publish the workbook model, the routine 300 continues to operation 306.

At operation 306, the spreadsheet client application 4 receives from the user a name for the workbook function. The name identifies the workbook which contains the function and the function itself within the workbook. The name may be utilized later by a calling application to identify the requested remote function call. Once the name has been received, the routine 300 continues to operation 308 where one or more cells may be identified by the user as the inputs to the function. At operation 310, the user may provide a text name for each of the inputs. For instance, a user may select a cell within the workbook to identify the cell as an input and then provide the name "Asset Price" to identify the input. Once the input cells and their names have been identified by the user, the routine 300 continues from operation 310 to operation 312.

At operation 312, one or more cells may be identified by the user as the outputs from the function. At operation 314, the user may provide a text name for each of the outputs. For instance, at operations 312 and 314, a user may select a cell within the workbook to identify the cell as an output and then provide the name "Call Value" to identify the output. Once the output cells and their names have been identified by the user, the routine 300 continues from operation 314 to operation 316.

From operation 314, the routine 300 continues to operation 316, where the workbook 6, including data defining the designated workbook function, is published to the spreadsheet server application 13. For instance, publication of the workbook 6 may include uploading the workbook 6 to the server computer 12A or programmatically generating a spreadsheet and sending it to the server computer 12A through a server application program interface ("API"). When the workbook 6 is published to the spreadsheet server application 13, the workbook 6 is stored in the repository 14. The spreadsheet server application 13 is also notified of the existence of the workbook 6 and the workbook functions defined within the workbook may then be exposed via web services. The data identifying the name of the workbook function and the input and output cells and their names is also published to the server 12A with the workbook.

Once the workbook 6 has been propagated to the repository 14 and analyzed by the spreadsheet server application 13, client applications, such as the SOAP-compatible program 8 or the spreadsheet client application 4, may be utilized to call the workbook function on the server computer12A. Additional details regarding the various functions performed by the spreadsheet client application 4 to call the function and performed by the spreadsheet server application 13 in order to expose the workbook function and to receive and respond to function calls will be described in greater detail below with respect to FIGURES 5-8. From operation 316, the routine 300 continues to operation 318, where it ends.

Referring now to FIGURE 4, an illustrative user interface will be described for publishing a workbook model that includes a workbook function. The user interface 30 shown in FIGURE 4 may be provided to a user in response to a user request to publish a workbook function to the server computer 12A. The user interface 30 may show a portion of the current worksheet 32. Each of the cells shown within the current worksheet 32 may be selected by the user to either identify the cell as an input to the function or as an output from the function.

In order to assist in the definition of the inputs to the workbook function, a user may select one or more cells within the current workbook 32. The user may then select the user interface button 36 to add the selected cell as a new input. The user may then enter a name for the input into the list box 34. In this manner, a user may define as many cells as necessary of the current workbook 32 as inputs to the workbook function. Similarly, the user may select one or more cells of the current workbook 32 and then select the user interface button 40 to designate the cells as outputs from the function. The list box 38 may then be utilized to provide a name for each of the input arguments. The example illustrated in FIGURE 4 shows a workbook 32 that defines a model for calculating call and put values for options. The cells C2-C7 have been defined as inputs and cells F2-F3 have been defined as outputs.

The user interface 30 shown in FIGURE 4 may also provide a text box 42 into which a name for the function may be typed by the user. The user may also provide a text description of the function in the text box 44. Finally, the user may identify the location at the server computer 12A at which the new workbook function should be published in the text box 46. Once the user has provided this information, the button 48 may be selected to publish the workbook, including the metadata describing the workbook function, to the server computer 12A.

Turning now to FIGURE 5A, an illustrative routine 500 will be described illustrating the operation of the spreadsheet client application 4 for defining and publishing a workbook function exposed by the server computer 12A. As discussed previously, it should be appreciated that the spreadsheet client application 4 is described herein as calling the workbook function. However, the workbook function may also be called by any other type of computer program that is compatible with remote function calls. For instance, other server computers, custom program code, other types of applications programs, and many other types of computer programs.

The routine 500 begins at operation 502, where a user utilizes the spreadsheet client application 4 to author a workbook in the manner described above. From operation 502, the routine 500 continues to operation 504, where the spreadsheet client application 4 determines whether a user has made a request to utilize a workbook function available from the server computer 12A. If the user has not made such a request, the routine 500 returns to operation 502 where the user may continue to author the model. If the user does request to utilize a remote workbook function, the routine 500 continues to operation 506.

At operation 506, the name of the requested function is received from the user. A list of available workbook functions and their parameters may be discovered and retrieved from the server computer 12A. Once the user has identified the remote workbook function to be utilized, the routine 500 continues to operation 508, where the user selects the workbook cells that should be utilized as inputs to the workbook function. In particular, the user assigns one cell to each of the inputs of the function. The data in the assigned cells may then be provided as inputs to the function when the remote function call is made. At operation 510, the user selects the workbook cells where outputs from the function should be placed in a similar manner. The routine 500 then continues to operation 511, where it ends.

Turning now to FIGURE 5B, an illustrative routine 550 will be described for calling a workbook function via a web services call. The routine 550 begins at operation 511, where data from the input cells along with the respective names of the input parameters for the function call are retrieved. At operation 512, the web-services call is placed to the requested function. At operation 514, the spreadsheet client application 4 receives a response from the server computer 12A including the outputs from the function call. At operation 516, the received outputs are placed into the workbook at the cell locations defined by the user for outputs. FIGURE 8 shows a portion of the workbook 70. As described above, the cells 72 and 74 were defined as containing the outputs from the workbook function. As shown in FIGURE 8, the values calculated by the workbook function that were returned to the spreadsheet client application 4 have been placed into the appropriate cells of the workbook 70. From operation 516, the routine 550 continues to operation 518, where it ends.

Referring now to FIGURE 6, an illustrative user interface will be described for generating a remote function call to a server-hosted workbook function. The user interface 50 shown in FIGURE 6 is displayed by the spreadsheet client application 4 in response to a request by a user to utilize a remote workbook function. The user interface 50 includes a display of the current workbook 52, including one or more cells of the workbook.

The user interface 50 also includes a list box 56 that identifies each of the inputs to the requested workbook function. The user may select any of the cells of the workbook 52 and then select the button 58 to assign the cell to an input of the function. Similarly, the list box 68 identifies by name each of the outputs of the function. The user may select any of the cells of the workbook 52 and the button 62 to assign cells of the workbook to the outputs of the function. Once the user has assigned cells of the workbook 52 to each of the inputs and outputs, the user may select the user interface button 64 to place the desired remote function call.

Turning now to FIGURE 7, an illustrative routine 700 will be described illustrating the operation of the spreadsheet server application 13 for receiving and responding to calls directed toward a workbook function exposed via web services. The routine 700 begins at operation 702, where the spreadsheet server application 13 exposes the available workbook functions. Once the spreadsheet server application 13 has exposed the various workbook functions, a client application such as the SOAP-compatible program 8 or the spreadsheet client application 4 may discover the available functions and issue calls directed to a specific function.

The routine 700 continues from operation 702 to operation 704, where the spreadsheet server application 13 receives a remote function call directed toward a specific workbook function. The call includes data identifying each of the inputs to the function and providing values for each of the inputs. From operation 704, the routine 700 continues to operation 706, where the spreadsheet server application 13 loads the workbook 6 containing the workbook function to which the received call was directed. Once the workbook 6 has been loaded by the spreadsheet server application 13, the routine 700 continues to operation 708, where the spreadsheet server application 13 populates the appropriate cells of the loaded workbook with the inputs provided with the web services call. The routine 700 then continues from operation 708 to operation 710.

At operation 710, the spreadsheet server application 13 determines whether the workbook 6 includes a reference to another data source or another workbook function. For instance, as described briefly above, the workbook may include a reference to a data source, such as the data source 16. If the workbook 6 includes a reference to another data source, the routine 700 branches to operation 712, where the spreadsheet server application 13 queries the data source 16 for any data needed to calculate the workbook 6. Once this data is received by the spreadsheet server application 13, the workbook 6 is updated with the received data.

If, at operation 710, it is determined that the workbook 6 does not include a reference to another data source, the routine 700 continues to operation 714. At operation 714, the spreadsheet server application 13 recalculates the contents of the workbook 6, including calculation of the workbook function. From operation 714, the routine 500 continues to operation 716, where the spreadsheet server application 13 retrieves the contents of cells of the workbook model that were identified as outputs when the workbook function was defined. The routine 700 then continues to operation 718, where the spreadsheet server application 13 prepares a web services reply that includes the data from the outputs of the workbook function. At operation 720, the reply is transmitted to the client computer 2 as a response to the initial web services request. The client computer 2 may then place the received output data into the appropriate cells in the manner described above. The routine 700 then continues from operation 720 to operation 722, where it ends.

Based on the foregoing, it should be appreciated that the various embodiments of the invention include a method, system, apparatus, and computer-readable medium for exposing and calling workbook functions via web services. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.