Hello, pro ver 4.532, sco unix.

Does SET_CURR work correctly using C-ISAM files?

I'm having problems with it which I'll describe in detail if it is known to work....

Rob

Hi,

There is a bug with SET_CURR when using expand mode and @PSEQ in paging screens.

If you set SET_CURR, press expand mode, go into change mode and then arrow down the paging screen until you get a new page, @PSEQ is set to 1 again.

Rob

Rob,
Have you used SET_CURR on an Alt-index to a cisam file?

The problem I'm having is shown below. I call another pgm to modify an invoice picked from the Select Screen. The modify pgm links back to the Select Screen. Using SET_CURR the cursor starts at the orig invoice , but it appears again below on the screen.

Select Scrn, 1-st time:
1 G94224 23.10 125
2 G94225 17.55 126
3 G94226 23.70 147 << invoice picked
4 G94227 39.60 402
5 G94228 17.70 489
6 G94229 14.24 845

Select Screen on return:
3 G94226 23.70 147 < 4 G94225 17.55 126 ..
5 G94226 23.70 147 < 6 G94227 39.60 402
7 G94228 17.70 489
8 G94229 14.24 845

I use the following in the ls's DEF LOGIC:
IF @$COM2 = 'SCRN'
AR_TREF = @$COM4
SET_CURR(AR_TREF)
ENDIF
The above is done after a SEL-ONLY(ACSH_DMCODE)

The alt-ix is defined as:
MS ACSHX1
M ACSH_DMCODE
M SALES_WEEK
M AR_TREF
ME


Thanks in advance
Rob F

After looking at your function, I have found a bug with PRO-IV.

Using SET_CURR with a Sort/Select set to Y causes random errors and core dumps!!!!

Rob