Call the background stored procedure in ACCESS. ACCESS is an excellent front-end development tool of ClientServer. it is easy to learn and use, user-friendly, simple to develop, and flexible with other database interfaces. However, ACCESS is an excellent front-end development tool for Client/Server when processing a large amount of data. it is easy to learn and use, user-friendly, easy to develop, and flexible with other database interfaces. However, it is slow to process a large amount of data. There are currently 0.6 million users in Shenzhen Power Supply Bureau. There are 6 business offices connected to the bureau through 64 k ddn. if there is a business office that will process 10 thousand users, it will take 2 ~ 3 hours, seriously affecting the development of other services. Therefore, when a large amount of data needs to be processed, the data cannot be processed on the Client, but must be processed on the Server.
However, ACCESS and Server are mostly connected through ODBC, which increases the difficulty of calling backend stored procedures. Through long-term exploration in practical work, I can use the following three methods to call the background storage process according to different business needs.
1. Access submits jobs to the backend. each job corresponds to one stored procedure. In SQL Server 6.5, tasks are created through Task Manager, while in Oracle 8.0, jobs are created through Managing Job Queue. In Access, insert a job into the job_list table, which is generally run once every night. The businesses corresponding to these jobs generally need to process a large amount of data, but the real-time performance is relatively low. in our business, a typical example is a large amount of electricity computing every night.
2. create some triggers on the Server and activate these triggers in Access. Both SQL Server 6.5 and Oracle 8.0 are implemented through Create Trigger. In Access, different triggers are activated by inserting, modifying, and deleting records based on different services. One example of our business is that when the business personnel modify the user's electric meter reading, the trigger for calculating the electricity bill is activated and the user's electricity bill can be recalculated immediately. In this way, you can share the same program with batchcompute and do not need to re-develop it on the Access end, which can speed up front-end response.
3. the preceding two methods can only be used to indirectly call the background stored procedure. Access also provides a method for directly calling. you can use Access to transmit queries and directly send commands to the database server.
The procedure for creating an Access transfer query is as follows:
(1) click the "query" tab in the database window, and then click the "new" button.
(2) in the "new query" dialog box, click the "Design View" option, and then click the "OK" button.
(3) in the displayed table dialog box, click the close button.
(4) on the "query" menu, refer to "SQL statement conditions" and click "pass.
(5) on the toolbar, click "properties" to display the query attribute table.
(6) in the query attribute table, 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 "builder" button to generate the connection.
Bytes. However, when it needs to process a large amount of data ,...
