1) Access privilege control and log management are mandatory, and dbSheetClient has both functions as standard features.
2) The Excel worksheets are put under centralized administrative control.
3) Even without using the macro functions, dbSheetClient can achieve the same functionality , so the spreadsheet internal control issue can be addressed by dbSheetClient.
dbSheetClient can develop a Web-enabled system for any existing Excel-based work. For example, a business information support system, which analyzes data or makes a plan and schedule by using data from a mission critical enterprise system, or data shearing at a department/ section based on small scale databases such as petty cash management and address/document management are areas where dbSheetClient is often used.
Basically, you can use it to develop any kind of operation, though some are more fitting than the other. It is best fit for operations that Excel and SQL excel that, that is, classification, tabulation process, creating of a chart/graph for a reference system, as well as creating various forms. dbSheetClient is not the best for handling complicated structured forms. In the input form, dbSheetClient uses Excel sheets. So when you design the form, you should consider the features of the Excel to get a good result. Consequently, areas where users consider introducing dbSheetClient are, in many cases, related to work site operations where Excel is utilized.
The current version does not provide a function nor a dedicated DLL that enables end-users to modify the internal logic of the product.
dbSheetClient enables you to implement highly sophisticated systems by combining some 90 types of Task Types, which otherwise could be implemented partially by using macro functions. On top of this, the Task Types provide functions such as "Starting up external application" and "Call external DLL" to control the external processing, and by using these functions you can work with external programs, developed by different launguages, and DLL.
・It can construct a considerably full-fledged system.
・Since the data is entered using Excel, if you want to check the data integrity before updating the database, you need to have Excel perform the check function.
As a simple check function, you can limit the range of value input (ranged numeric values, character types, etc.) by using the "Data Validation" feature of Excel. You can also check validation using SQL before updating the database using the data in the worksheet.
・The dbSheetClient Server Version utilizes this feature to do duplication checks for the database, so duplication checks are realized automatically by dbSheetClient.
Concurrency Control is equipped as a standard feature of the Server Version. Optimistic Concurrency Control is set as a default in web system. Of course, the Pessimistic Concurrency Control is available, too.
dbSheetClient is a non-programming type development tool. Therefore, it is necessary to understand the idea and the structure of the tool. Also, Excel is a prerequisite to develop a system with this tool, which requires the developer to understand Excel.
Furthermore, even though this tool can generate SQL sentences to handle the processing with the database when it is simple one, complex processing must be implemented by generating SQL sentences by developers. This means the developer needs to possess a certain level of knowledge about SQL.
If you have these skills, according to our experience and past result, you can expect triple the productivity of conventional development approaches.
Especially, the more forms and tables there are, the greater your advantage (because you can re-use the forms and tables you made in Excel). In terms of the time it takes to educate SE, it takes two weeks to a month for a new member of our company to become eligible to develop a system with dbSheetClient. Once learned, these skills can develop more and more. An SE with one year of experience can ensure significantly high productivity.
1) PL Monitor
6 Windows; 4 Forms; 2 Master Tables; 4 Data Sets; 7 transaction worksheets; took one and a half months to develop
2) Sales Prospect System
13 Windows; 8 Forms; 3 Master Tables; 1 Data Set; 9 transaction worksheets; took one and a half months to develop
3) Petty Cash Management System
47 Windows; 24 Forms; 11 Master Tables; 13 Data Sets; 17 Transaction Worksheets; took four months to develop