FS1002: Record length exceeds max variable length (AREV Specific)
At 21 MAR 2002 07:40:21PM Tony Burke wrote:
I have a client that gets an FS1002 error whenever he tries to view certain records. I understand that this is a size issue but I'm not sure what to do about it. The application is running on AREV 2.12.
Any suggestions or instructions would be greatly appreciated.
Thanks in advance.
Tony Burke
At 22 MAR 2002 05:20AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Tony,
When the user first logs on, check the amount of memory available by typing WHO at AREV's TCL (hit F5). If it is less than 160K you may need to adjust the settings in the memory tab of the Windows shortcut to AREV.
You may also need to remove any existing rightdex or quickdex from the file (F6 from the dictionary windows).
If you offer details of your version of Windows there may be specific advice pertaining to your version.
World Leaders in all things RevSoft
At 22 MAR 2002 03:37PM Tony Burke wrote:
They're running Windows 98SE. I've checked the 'Who' status and available memory shows at 396636, Descriptors show at 2722, and Expanded is active.
They do have the Rightdex/Quickdex files and I get prompted to update them when I access them but I'm not sure what that means. If I do need to remove them how do I go about doing that?
Tony Burke
At 22 MAR 2002 04:25PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
At TCL:
DICT filename
Hit F6
It's either option 3 or 4 to Remove Quickdex or remove Rightdex accordingly.
You can always add a Btree on the key field as a replacement - this will support over 64K of keylist.
World Leaders in all things RevSoft
At 22 MAR 2002 08:27PM Tony Burke wrote:
I've tried removing Quickdex/Rightdex but that doesn't seem to of helped. I'm now getting a B703(Variable exceeds maximum length) runtime error. Is this the same as a FS1002 error?
At 26 MAR 2002 04:22AM Scott, LMS wrote:
Hi Tony
I was having problems like this in OI. I wrote a calculated field (symbolic? dictionary item) to display the record length ie in the formula bit put something like
@ANS=LEN(@RECORD)
This will show you if any record sizes are actually approaching 64K (sometimes 50K + is enough to mess things up).
If records are still well under, it could be the formatting that gets added when you load the record up for display or printing that blows the limits.
If this is the case, you might want to break the record up into fields, ie read bits into separate variables before formatting. This especially applies when you have multi row, multi column tables contained within your record structure. Table display entities tend to have smaller capacity. And formatting for money ie something that looks like 1235678 in the record and becomes $123,456.78CR, will decrease the amount of room available before you have a blowout.
Hope this helps
Scott, LMS