Re: GO_RECORD problem

From: Steve Cosner <stevec_at_zimmer.csufresno.edu>
Date: 1998/03/07
Message-ID: <6ds26v$ib8_at_info.csufresno.edu>#1/1

Go_Record(65534) implies that you have fetched at least 65534 records into your Forms block. This would probably take about a week to do... if your client had enough memory to store all the column values and related data for all those rows. I doubt that you have that many rows in your block, so I wonder what you are really intending to do with the go_record command.

Any time your form has more than a hundred or so rows in a block, things get pretty slow, and you probably need to find ways of querying fewer rows.

Steve Cosner

---

http://members.aol.com/stevec5088
Downloadable utility form -- Display and update any table.

In article <35015793.D7A645B6_at_interaccess.com>, Jim DeCicco <decj1_at_interaccess.com> wrote:
>Hi,
>
>A developer I'm working with is having a problem with GO_RECORD
>(GOTO_RECORD?) is Dev. 2K. The problem occurs when attempting to go to a
>record number > 65534. If anyone could help us get past this 'magic'
>number, it would be greatly appreciated.
>
>Thanks,
>
>Jim
>
Received on Sat Mar 07 1998 - 00:00:00 CET