Calling background stored procedures in ACCESS_PHP tutorial

ACCESS is an excellent front-end development tool for Client/Server. It is easy to learn and use, has a friendly interface, is simple to develop, and has flexible interfaces with other databases. However, it is relatively slow when processing large amounts of data. Shenzhen Power Supply Bureau currently has 600,000 users, and has 6 business offices below, which are connected to the bureau through 64K DDN. If one business office wants to handle 10,000 users, it will take 2 to 3 hours, seriously affecting the development of other businesses. Therefore, when there is a large amount of data that needs to be processed, it cannot be processed on the Client side, but must be processed on the Server side.
However, most connections between ACCESS and the server are through ODBC, which increases the difficulty of calling background stored procedures. Through long-term exploration in actual work, the author can use the following three methods to call background stored procedures according to different business needs.
1. Access submits jobs to the background, and each job corresponds to a stored procedure. In SQL Server 6.5, the corresponding Task is created through Task Manager; in Oracle 8.0, the corresponding Job is created through Managing Job Queue. In Access, insert a job in the job_list table. These jobs generally run once every night. The businesses corresponding to these jobs generally need to process a very large amount of data, and the real-time performance is low. A typical example in our business is the calculation of a large amount of electricity bills every night.
2. Create some triggers on the server side and activate these triggers in Access. In SQL Server 6.5 and Oracle 8.0, this is achieved through Create Trigger. In Access, different triggers are activated by inserting, modifying, and deleting records according to different businesses. An example in our business is that when the business staff modifies the user's electricity meter reading and activates the trigger to calculate the electricity bill, the user's electricity bill can be recalculated immediately. In this way, you can share the same program with batch calculation of electricity bills without having to re-develop it on the Access side, which can speed up the response speed of the front-end.
3. The above two methods can only be said to be indirect calls to the background stored procedures. Access also provides a direct call method. You can use Access to pass the query and directly send the command to the database server.
The steps to create an Access delivery query are as follows:
(1) Click the "Query" tab in the database window, and then click the "New" button.
　(2) Click the "Design View" option in the "New Query" dialog box, and then click the "OK" button.
(3) Click the "Close" button in the "Show Table" dialog box.
(4) On the Query menu, point to SQL Statement Conditions, and then click the Pass command.
　(5) On the toolbar, click the Properties button to display the query property table.
　(6) In the query attribute table, please set the "ODBC connection string" attribute to specify the database information to be connected. You can enter the connection information: "ODBC;DSN=ntserver0;UID=sa;PWD=;DATABASE=BMS", or use the "Generate" button to generate it.

http://www.bkjia.com/PHPjc/631162.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/631162.htmlTechArticleACCESS is an excellent front-end development tool for Client/Server, which is easy to learn and use, has a friendly interface, is simple to develop, and Other database interfaces are flexible. However, when it needs to process a large amount of data,...