More "Memory could not be read/written" (GRX)
Chris Sellitto
sellich at guaranteedreturns.com
Tue Oct 9 08:22:05 PDT 2007
All,
I want to share with you all a recent experience I had with the "Memory
could not be read/written" error. I had a selection process where the
user could select items from a listbox. When they were finished
selecting all their choices, I built a variable that contained all of
the items they had just chosen, (I know this is probably not the best
way to do it, but it was easy, and it worked for us at the time), using
the SHOW command. Well it worked fine for about a year, until last
week, when the user was getting this error. After some debugging, I
found that the error always occurred on this SHOW command to display the
variable. The variable was not defined, as I did not know how many
items would be selected. Also, the difference was that they were
selecting many more items than usual. This made the variable longer
than the length of the screen (80 characters), and this is why I believe
the error was occurring, because when you select less items, it would
run fine, without errors. I resolved this issue by displaying these
items in a MSGBOX and using the \n option.
Sorry to make a short story long, but maybe it might help someone else
having a similar problem.
Christopher Sellitto
VP Computer Operations
Guaranteed Returns
More information about the Filepro-list
mailing list