Yes, it is.
When you log on with Supervisor privileged user ID after starting up the dbSheetClient Development component, Import AD information becomes available. In the Edit window, you can browse the OU (Organizational Unit) and Groups in the AD in a tree-shaped structure, then you can link the target in the Edit window to the group you registered from the Server administration window of the dbSheetClient and register it as the dbSheetClient user. Whenever there is a change of a member at the AD side, it is necessary to import it.

It is feasible to modify the portions which do not affect to the linkage to the database.
In that case, you can modify the format of the table, formula, cell and character freely.

１．When it is for data query only and there is no need to output data to the Worksheet:

①The data can be easily displayed to the data viewer (data query window, data query window with search function), which is included in the basic component of the dbSheetClient.

2．When you need to output the data on the Excel Worksheet:

①If you try to output data which exceeds the maximum number of rows it becomes an error, so you need to limit the data cases to import by an SQL sentence lest it will not exceed the maximum number of rows.

②It is feasible to divide the data, ie: from 1 to 65536, from 65537 to ... on the plural Worksheets.

③ In Excel 2007, the maximum number of rows you can output data can become up to 1,048,576 rows.

We recommend you to apply SSL to your dbSheetClient Server.
The communication pathway is encrypted by SSL but irreversible encryption is applied for password.
For other items, the security method that .Net Framework provides is used.
Specifically, measures for user authentication, log on, safe session management and safe database connection are taken.

No problem.
By making two projects such as XX Project and XX_under_dev Project, you can administer them. However, if emphasis is placed on the safety from the stability and security aspects in executing them on the official machine, separation of servers is recommended.

It is possible for developers to develop off-line with the Development component, but it is not possible for end users to execute a program off-line with the Runtime component. The operation log of the Runtime component is controlled by the Server side, so that execution is permitted only in the environment which is connected online.
However, it is possible to have the following process implemented as a part of workflow by the dbSheetClient Development component: you can save work data as a worksheet locally while operating the Runtime component on-line, and after changing data off-line on the same form of the worksheet you can incorporate the data changed when Runtime component is connected to the Server via LAN or internet.

dbSheetCient can deal with image files.
Our Task Type is equipped with Insert figure, Clear figure and File upload as standard functions which enable JPEG and GIF files to be displayed dynamically.
For a CAD drawing, it became compatible from Ver.3 and later by starting up specialized external software.

ClickOnce is a Microsoft technology for software update and distribution, which is compatible with .NET Framework and the above application. As a result, the following can be achieved:

① Even the user without administrator's privilege can install the program.

② The automatic distribution of the latest dbSheetClient becomes feasible. Exactly speaking, when the application is started up, the program checks if there is an update on the Server, and if there is, the message, Do you wish to update? is displayed. By selecting Yes, the latest application is downloaded to be executed.

③ Since you can start up the application from the portal site, you can start up the dbSheetClient from the groupware or the hyperlink of the Web application.

① In the dbSheetClient, the privilege is classified as follows and managed.
・System administrator privilege
・Developer privilege
・Project execution privilege
・Task execution privilege

② The system administrator privilege, developer privilege and project execution privilege are set by the dbSheetClient Server side, and the task execution privilege is set by the Development component on every Menus and Buttons according to groups, to whom each user belongs.

③ For more advanced privilege setting, you can conduct a privilege management based on your own privilege management table by combining Tasks.

① Content covered by operation log
(common matter)
1: Project name, 2: User name 3: Terminal PC name 4: System component
5: Excel version, 6: OS, 7: Date, 8: Operation outline
(When saving or printing)
9: Book name, 10: Worksheet name

② When you want to extract an operation log of a particular part of a Project separately, you can get it by setting the Task Type Log information writing on the corresponding process of a Project of the particular part.

No, not all of them are saved. Operations that will be registered as log information are as follows.
When the following operations are conducted, the operation log is automatically recorded in the log information
1) Login time (Since any Project are not selected at this moment, the Project name is blank)
2) When a Project is selected in Runtime/Development component
3) When a Project is ended in Runtime/Development component
4) When Save/Print is executed in the Runtime component.
5) When various types of upload, such as Project Definition, are executed in the Development component.
6) Logoff time (When it returns to the login screen).
7) Terminal logoff time (When the dbSheetClient exited).
For all other operations, only when the Task Type, Log information writing is executed, the corresponding operation log is recorded.

① Error detection can be implemented by using Excel's input rule function or conditional formatting. Moreover, the error determination can be run by using other Excel functions on the Excel sheet.

*Even when error check is not conducted, mismatching of data and/or overlapping error is found at the data update time, the dbSheetClient shows an error message.

To ensure the security of the system, only when the developer permits, the data can be saved to the CSV and the Excel Workbook can be saved.

① By default, the optimistic lock method (optimistic concurrency control) is adopted as a standard. Therefore, you can update the data only after you check if the data is not changed after you acquired the data and before you change the data. If someone else has already updated the data, it becomes an error.

② dbSheetClient is compatible with the pessimistic lock method, too, that applies the lock to the records of the data before you download them.

In the normal agreement (except a limited individual agreement), there is no restriction on the number of Projects to be registered.

When the Project is uploaded with the project name of the current operation, it is reflected at once.
However, if someone is executing the Project at the time of uploading, it will be reflected when the Project is terminated and executed again.

dbSheetClient can set role based access control on the Menu and/or Button in the Project which shares the same Excel Workbook/Worksheet.

1) Usually, when dbSheetClient controls data with protected cell, the Worksheet will be unprotected automatically, and after the processing is over, the Worksheet will be protected again. So update is feasible.

2) The dbSheetClient opens an Excel file with the read-only mode. In this case, usually users cannot display the Ribbon, so the Excel file, which is opened with the dbSheetClient, cannot be saved. However, dbSheetClient has the Task Type, “Save” to save the Excel Workbook, so by using this Task Type, it can save the file with a different file name.

dbSheetClient manages the Project information with 14 kinds of tables such as Database definition, Workbook definition, Menu definition, Task definition and Query definition, and so on. The Development component has referrence output function, so it can produce each tables information in the form of Excel file.