hm, ok, but the Problem is elswhere... In the Program, the structure is the mainproblem. There are several functions that call each other, if I press the 'Next Dataentry'-Button, several minor-functions are called until finaly(in another function) the 'Select Next/First...' is called. The Problem is that for every Next/Prev there will be another 'Select...'-Statement with a temporary Result-Set, and there I always get the first or last Dataentry, because the curser is always reseted. And I can't do big changes to the Program-Structure because the Prog is huge(several 100 Files) that mostly depend on each other, most program-functions and also other Progs use this 'Select next/first...'-functions. I could do a initial 'Select...'-statement followed by 'fetch next/prev' for each button-call, but for that I would have to change the programstructure dramatically... (by pulling up the select/fetch calls into the parent-functions, but then other progs couldn't access them and so on)
There, I hope that explains the situation :) Isn't there a quick and clean workaround for that? -----Urspr�ngliche Nachricht----- Von: Dittmar, Daniel [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 23. Dezember 2004 16:28 An: Hoelker, Juergen; [email protected] Betreff: RE: SELECT NEXT >is there a better solution for exchanging SELECT NEXT(from >Adabas)-Querys >with SELECT and FETCH NEXT?? >This seems not to work somewhat, I get everytime only the >first Dataentry... >Or am I making something wrong? What would be the wright >Syntax for that? - Execute the SELECT once. You probably have to change it to restrict the rows that you get (WHERE keycol BETWEEN <first> AND <last>). An 'ORDER BY keycol' is also required if you want to get the rows in the same order as your Adabas D program did - Execute FETCH NEXT until the cursor is exhausted. Daniel Dittmar -- Daniel Dittmar SAP Labs Berlin [EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
