variable not holding value

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
[mailto:filepro-
> list-bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of George
> Sent: Friday, November 20, 2009 2:41 PM
> To: rkreiss at gccconsulting.net; fpsupport at fptech.com; filepro-
> list at lists.celestial.com
> Subject: RE: variable not holding value
> 
> That's why I define all my dummy fields and variables in automatic
> processing.
> 
> -----Original Message-----
> From: filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
>
[mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com]
> On Behalf Of Richard Kreiss
> Sent: Friday, November 20, 2009 2:06 PM
> To: fpsupport at fptech.com; filepro-list at lists.celestial.com
> Subject: variable not holding value
> 
> Windows XP, Server 2008, filepro 5.6.07
> 
> I have a program which has been working for almost 5 years and now has
> developed a big problem.
> 
> The program sits on 1 record.  At @entsel, a lookup is done to a file to
get
> a 4 digit code and a demand index number to use.  The values a placed in
> long variables.  The routine the uses the index number to display a
browse.
> A displayed record is selected and another browse is opened and @bk
prompts
> are displayed.
> 
> Once a key is pressed, specific values are posted to the displayed record.
> Pressing <X> reruns the original browse.
> 
> This browse is constructed using dummy fields to hold the appropriate
> values.
> 
> What I have found is that all variables are now losing their values when
any
> @bk key is pressed unless I make it global.
> 
> Anyone have any idea why this should be occurring now?
> 
> 
> Richard Kreiss
> GCC Consulting
> rkreiss at gccconsulting.net

George,

As I indicated, this program has been working fine for almost 5 years.  In
fact, my client is using it currently using 9 other data sets using other
demand indexes.  This one index set is causing the problem.

This app, the user sits on one record only, all variables are defined in the
current table.  Nothing in the code blanks any of the primary variables.
The only variables that get blanked are specific to the record being
updated.

Richard