CodePudding user response:
Write a stored procedure, and then ado calls the stored procedureCodePudding user response:
Call osql to performCodePudding user response:
To carry out calling ado controls the AdoStoredProc controlsCodePudding user response:
Methods:Use stringlist load SQL file, read line by line,
=GO, adoqry execution, empty adoqry. SQL
<> GO, after reading the writing adoqry. SQL
CodePudding user response:
Points to perform adoqry ExecSQL many timesCodePudding user response:
My SQL haven't tried this problemSuch as: batch to create tables and views are not error
The reason should be on the SQL, try to don't refer to the SQL database export, write their own, remove the those irrelevant words
Such as: DBO aTable, aTable instead
CodePudding user response:
1, starting the transaction processing functions on the ADO connection control2, in a transaction, use the query control respectively carry out the update of different views,
3, the transaction is committed or rolled back when an error occurs,
CodePudding user response:
Replace the GO try with a semicolonCodePudding user response:
Itself is not supported, because GO out of the things, that are commonly need to use software in the design of automatic updates, I usually use SQLCompare automatically generate a file, and then use adoquery execution