Transaction in R/Basic (AREV Specific) [Revelation On-Line Wiki]

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 28 MAR 2000 05:00:52AM Maria Cramer wrote:

AREV Specific

Hello,

I want to use transaction control in the next situation ?

Table A and Table B ? are warehouses, contains any rows (network environment).

Each row of these tables contains field ?Quantity? (for example).

Task:

R/Basic procedure transfers some items of some rows from Table A to Table B.

Question:

Where in my R/Basic procedure I can use TRANSACTION ON, TRANSACTION COMMIT,

READ FROM A, WRITE TO B, and may be something else ?

Thanks,

Maria

At 28 MAR 2000 05:47PM Mike Ruane, WinWin Solutions Inc. wrote:

Maria-

The flow would usually be:

TRANSACTION ON

READ FROM B THEN
WRITE TO A THEN
  TRANSACTION COMMIT
END ELSE
  TRANSACTION ROLLBACK
END
END

Hope it helps-

Mike Ruane

WinWin Solutions Inc.

WWW.WinWinSol.Com

At 31 MAR 2000 03:20AM Maria Cramer wrote:

Thanks Mike.

Additional questions:

1. Have any reasons use lock and unlock

TRANSACTION ON

lock A, key_row then

READ FROM B THEN

WRITE TO A THEN

unlock A, key_row

end

TRANSACTION COMMIT

END ELSE

TRANSACTION ROLLBACK

END

END

2. "User's Guide" contains next information " or a call to the R/BASIC TRANSACT subroutine ".

I cannot find TRANSACT subroutine in any AREV Documents !

Maria.

At 31 MAR 2000 10:44AM [email protected] wrote:

Maria,

pmfji ..

If you question is .. is there a reason to use locking then the answer is YES.

The transaction block does nothing other that save all updated until a specific time (COMMIT). This does not mean that others are not trying to update the same records.

By locking a record .. other processes are not allowed to access that record until it is released. This is most important if you have any User access (screens). The lock (along with window messages etc) warns the user that something is happening to the record and they can't modify it. It also warns the process that something is happening to it. This could trigger your logic to see if you want to commit the transaction or not.

Always .. always always use locking. It is one of those good habits.

[email protected] onmouseover=window.status=imagine … a company that supports it products with pride not extortion;return(true)"

David Tod Sigafoos ~ SigSolutions

cell: 503-341-2983

View this thread on the forum...