>1. Your write just one generic procedure which accept parameters: field name and up/low limits.
>2. Your run this procedure (one SQL statement with Where BETWEEN(&fieldname..) ahd get cursor.
>3. Then you change your parameter and call the same procedure again against new created cursor
That will sure work, but then you have to create a bunch of cursors and anneal them when done, plus remove duplicate references back to the parent table (requiring an additional INDEX UNIQUE command or something similar). So I again refer to the title of the thread.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only