More "Memory could not be read/written" (GRX)

[Chris Sellitto]

Thanks for the suggestion Nancy.  We actually are doing pretty much the
same exact logic in some
of our other selection routines.  I guess it is just being lazy, due to
too many other projects to
work on, that we did not employ it on this particular process.

Thanks again
Chris

P.S.  Does anyone know why it would cause the memory error?

> Chris Sellitto wrote:
> > 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
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> > 
> > 
> You might want to load the selection list into an array that 
> could be displayed with listbox.  This allows them to scroll 
> around and could give you some edit possiblities.
> 
> I have also done this by writing the selections to a file, 
> with a list variable.
> 
> For example,  the file has fields like this:
> 
> List Name	15
> Account		10
> 
> They indicate a list name at the start of the selection and 
> then I ask for accounts until they are finished.  Each is 
> added to the selection file.  It can then be used in many 
> ways.  Each list can be managed separately.  They can reuse a 
> list as many times as they want.  Stuff like that.
> 
> Then as the selection is done, I just do a quick lookup to 
> the file using an index built on both the fields, and if I 
> have a match I select, if not I don't.
> 
> This kind of file can be used for all kinds of complex 
> selections.  Just make sure you allow for multiuser options 
> if that would be an issue.
> 
> Nancy
> 
> 
> -- 
> Nancy Palmquist 		MOS & filePro Training Available
> Virtual Software Systems	Web Based Training and Consulting	
> PHONE: (412) 835-9417		   Web site:  http://www.vss3.com
>