The key is to design a job.
1
Do not use unconditional
SQL
Scriptures.
Select * from table
Such statements can make your service
The server crash, my approach is to write a method to send the customer's data request to the server, the server is initially
Modified
SQL
Conditional parameters. Then, the client is only
Open.
Although this is troublesome, it gets a speed advantage.
2
, Do the information as much as possible on the server, give the results to the client, do not take the data from the server
Go to the client. For example, I want to get a user's menu permission, I only pass the user number to the server, service
The device is inquired, processing, and finally returned the result with the parameter, and does not use any data components at all.
3
And define some of your own methods. Use the method to process customer requests. Only have to use a data sheet connection
Just use
ClientDataSet.
4
For functional things, such as some
"
Posting
"
Processing, don't move to the client, customer
The end needs to be sent to the keyword to be processed to the server, all the processing is done on the server, the result is completed
That is prompted to the client.
5
It is necessary to distinguish between functional division. The client is the operator and the machine's conversation interface, the server is the result of the conversation
The way. Author Blog: http://blog.9cbs.net/davidvon
