I recently wrote a system for a client, running under the single well (asa9 database), single user proposed recently, need to put the system into a network system, many users use the
So I just changed to SQL server 2000 database, server environment is Windows server 2003 + SQL server 2000, connect to the database parameter is:
The SQLCA. DBMS="OLE DB"
The SQLCA. LogPass='660808'
The SQLCA. LogId="sa"
The SQLCA. The AutoCommit=false
='SQLOLEDB' SQLCA. DBParm="PROVIDER and DATASOURCE='SPPH - E57E4C2855, PROVIDERSTRING=' database=physics'"

The question is: when there are multiple users enter the system, if a user after to do data updates, if saving data, appear crash (mouse into a funnel) phenomenon, if other users to exit the system at this moment, is successfully saved, funnel disappear, then I put the connection parameters SQLCA. The AutoCommit=false to the SQLCA. The AutoCommit=true, problem solved, but this has not solve the problem of concurrent, prawns, please help me, I'm try so hard, thank you

CodePudding user response:

Normally, connection parameters almost anything

CodePudding user response:

refer to the original poster ZPY01234 posts:

I recently wrote a system for a customer, in a single machine running well (asa9 database), single user proposed recently, need to put the system into a network system, many users use the
So I just changed to SQL server 2000 database, server environment is Windows server 2003 + SQL server 2000, connect to the database parameter is:
The SQLCA. DBMS="OLE DB"
The SQLCA. LogPass='660808'
The SQLCA. LogId="sa"
The SQLCA. The AutoCommit=false
='SQLOLEDB' SQLCA. DBParm="PROVIDER and DATASOURCE='SPPH - E57E4C2855, PROVID...

Obvious signs is locked, normal also showed that, after the modification of the AutoCommit

Check your script, in dw. After the update, should have corresponding to commit or rollback

CodePudding user response:

Upstairs friend said is right, my script in dw. After the update, there is a corresponding commit or rollback,
However, if there are embedded in the script update, the SQL statements such as insert, need not commit, the data updated
And my idea is in the update, insert statement after judging the value of the sqlcode, then perform a commit or rollback, don't know how to solve this problem, thank you

CodePudding user response:

Put your practice in the PB9 try, is not appear this kind of phenomenon, ha ha, after the PB10, your connection statement should be something less

CodePudding user response:

Excuse me upstairs to the elder brothers, what my connection parameters less, can you tell me? thank you

CodePudding user response:

I also upgrade to 10 that only appeared well after this issue, then add a COMMIT all solved

CodePudding user response:

Data window in updates to the database, you have to commit or rollback immediately, if this between, in the pop-up window appears, for example, pos when receive money, money is opened, dw_1. The update ()

Change, return again, if this time again commit; Other pos will appear feign death phenomenon, this phenomenon will not appear on the single, I think that has nothing to do with the version of pb

CodePudding user response:

Use the oledb to connect to the database when it comes to such

Add:

The SQLCA. Lock="RC"

Can solve the problem

CodePudding user response:

Use the oledb to connect to the database when it comes to such

Add:

The SQLCA. Lock="RC"

Can solve the problem