Oops I was hopeful that Darren's solution would work. The Lsexit exited the selection cycle but did not drop the records in the list box. What did I miss doing? Darren any thoughts?
Frank
- ProIV Resource Centre
- → Viewing Profile: Posts: Frank Coppola
Community Stats
- Group Members
- Active Posts 11
- Profile Views 4,397
- Member Title Member
- Age 72 years old
- Birthday December 18, 1952
-
Gender
Male
-
Location
Red Bank NJ, United States
Previous Fields
-
First Name
Frank
-
Surname
Coppola
-
Nationality
US
-
Year Started ProIV
1990
-
Highest ProIV Version Used
5.5
-
Company Working For
Megasys Ltd
0
Neutral
User Tools
Friends
Frank Coppola hasn't added any friends yet.
Latest Visitors
Posts I've Made
In Topic: Limiting records in a list box
10 March 2006 - 02:49 PM
In Topic: Limiting records in a list box
10 March 2006 - 02:36 PM
Thanks everyone for your input. Darren your solution was exactly what I was hoping to find. It worked exactly the way I wanted.
When I get to the 501 record I save the key then enable a next Icon and lsexit. I also saved my start range to create a previous icon. It worked just as I hoped without the need for temp files.
Thanks
Frank
When I get to the 501 record I save the key then enable a next Icon and lsexit. I also saved my start range to create a previous icon. It worked just as I hoped without the need for temp files.
Thanks
Frank
In Topic: Limiting records in a list box
09 March 2006 - 03:01 PM
Thanks Anthony for your reply. However I did try that previously and it works if you are selecting records in key order. If you do any kind of order by then you can actually be missing records because the ROWNUM is assigned before the reordering.
Eaxmple:
Let's say the key is INVOICE NUMBER if the list box is selecting records ordered by invoice number ROWNUM works fine. But if
you select by SHIP DATE. ORDER BY SHIP DATE it will seelct the first 500 records that meet the criteria. leaving out other invoices that may fall somewhere in the range but have a higer invoice number.
This is exactly what happened at one customer site. The customer was complaining that not all the records were being displayed. We realized that ROWNUM was assigned before the orderby.
I was hoping there was someway to control the data in PRO-IV.
Thanks again,
Frank
Eaxmple:
Let's say the key is INVOICE NUMBER if the list box is selecting records ordered by invoice number ROWNUM works fine. But if
you select by SHIP DATE. ORDER BY SHIP DATE it will seelct the first 500 records that meet the criteria. leaving out other invoices that may fall somewhere in the range but have a higer invoice number.
This is exactly what happened at one customer site. The customer was complaining that not all the records were being displayed. We realized that ROWNUM was assigned before the orderby.
I was hoping there was someway to control the data in PRO-IV.
Thanks again,
Frank
In Topic: LIST BOX REFRESH IN VIP
08 March 2006 - 05:27 PM
I have had the same problem. The user clicks to sort on let's say a date column. Select a record that calls a Global function then
when the global is exited the list box refreshes but is sorted by the original sort not the date.
Have you been able to overcome this issue?
when the global is exited the list box refreshes but is sorted by the original sort not the date.
Have you been able to overcome this issue?
In Topic: VMS end of life and possible problems.
18 April 2003 - 01:58 PM
Hi Chris,
We have not used VIP yet but do use DEV Studio. It works fine. We did have a problem initially when trying to use Dev Studio on Open VMS 7.2. We installed a patch to TCPIP and that fixed the problem.
Frank
We have not used VIP yet but do use DEV Studio. It works fine. We did have a problem initially when trying to use Dev Studio on Open VMS 7.2. We installed a patch to TCPIP and that fixed the problem.
Frank
- ProIV Resource Centre
- → Viewing Profile: Posts: Frank Coppola
- Privacy Policy