Forum Post: RE: Accessing temp-tables in a dataset?

Status
Not open for further replies.
S

Simon L. Prinsloo

Guest
My previous postI was wrong. The assignment in the following part of your code is of no meaning, as the variable is immediately overwritten with the output of DoWork(): hdlEntity = DATASET dsEntity:HANDLE. DoWork(OUTPUT hdlEntity). This means that the handle may point to a another dataset from the one you defined and the dynamic code is the only safe option. On the other hand, if you use an "OUTPUT DATASET dsEntity" parameter, as suggested by Mike, my previous post will apply.

Continue reading...
 
Status
Not open for further replies.

Similar threads

D
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Passing object (input-output), with a dataset or TT, between client- and appserver-sess
Replies
0
Views
478
DenDuze
D
B
Problem with dynamic temp-table. Exceeding temp-table limit 32762
Replies
6
Views
3K
Stefan
Stefan
D
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: Double jeopardy when a NO-UNDO temp table violates a uniqueness constraint
Replies
0
Views
507
dbeavon
D
D
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Passing object (input-output), with a dataset or TT, between client- and appserver-sess
Replies
0
Views
506
DenDuze
D
M
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Garbage collection for the sake of static temp-tables (in long-running _progres)
Replies
0
Views
774
Mike Fechner
M
Top