Kbase 16833: Report Builder and Transaction scoping - database update.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Report Builder and Transaction scoping - database update.
Can report builder access new tables, records created in the 4GL
session?
In this scenario, the first thing to look at is the transaction scope.
Is the transaction that creates these records closed before the user
runs Report Builder?
To test this put MESSAGE TRANSACTION. right before the RB call.
If the message says "Yes", you are in transaction scope, and you
should probably make the transaction scope smaller.
For information on this see Programming Handbook chapter called
"Transactions".
In version 8.1 there is a section called "Controlling where
Transactions Begin and End" that will probably be helpful.
Especially helpful is a section called "Making Transactions Smaller".
This is in Chapter 11 of Programming Handbook.
If you do a COMPILE with a LISTING option, it will give a "Block
Report" at the end of the listing file that says for each block,
whether a transaction was started in that block.
If the transaction in which these new records were created is still
open, then Report Builder will not see them since Report Builder works
by making its own separate connection to the database.
AMH 4/28/97
Progress Software Technical Support Note # 16833