The best way to do that is to set subfile size 1 greater than subfile page and then just load all of your records to the subfile before displaying it. When you’re only talking 30 records then that is the best way to do it. It sounds like you are using SFLINZ and then chain/update; the SFLINZ will write all 500 records to the subfile and then use chain/update to write the 30 actual records.

It sounds like you might be using SFLINZ to cause blank records to be included in your subfile. There shouldn’t be any empty pages to display. If you don’t create them, they won’t be there.

It doesn’t really matter if you set SFLSIZ() to 500 or to the (size of a page + 1). The system only cares if the size is greater than what fits on a page. Ideally, you should set SFLSIZ() to the size that will fit perhaps 90% of its uses. But if it is expected to exceed the size of a page at any time, then it should be at least one greater than subfile page size. Setting the size to something that you expect allows the system to allocate appropriate memory when the subfile is first opened. Additional memory extensions are then minimized. (Subfiles are built in memory.)

Tom

thank you very much vatchy & TomLiotta, the problem has been solved now. Its because of the SFLINZ.

Generally, you would use SFLINZ to create an empty subfile. This could be a subfile that you want the user to enter records into. It can provide a method of data entry where the user types a group of records and your program processes the records as a group or a ‘batch’.

I haven’t run across other uses for it, but maybe someone else can describe others.

Tom