Insert a BROWSE of KeepStaffOutBGU right before that SELECT statement and make sure the table contains what you think it contains. -- Larry
________________________________ From: Charles Parks <[EMAIL PROTECTED]> To: RBASE-L Mailing List <[email protected]> Sent: Tuesday, October 28, 2008 2:36:52 PM Subject: [RBASE-L] - RE: [BULK] [RBASE-L] - Re: Lookup Variables in Timer I have changed the variable name but seem to be getting the same result. SELECT AllowIn, OkayToBeInBGU, KeepStaffOutBGURecNo + INTO fAllowIn INDICATOR fiAllowIn, + fOkayToBeInBGU INDICATOR fiOkayToBeInBGU, + fKpStfOutBGURecNo INDICATOR fiKpStfOutBGURecNo + FROM KeepStaffOutBGU + WHERE ForceOut = .fForceOut I'm using V-8. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Lustig Posted At: Tuesday, October 28, 2008 11:40 AM Posted To: RB7-L Conversation: [BULK] [RBASE-L] - Re: Lookup Variables in Timer Subject: [BULK] [RBASE-L] - Re: Lookup Variables in Timer Importance: Low << SELECT AllowIn, OkayToBeInBGU, KeepStaffOutBGURecNo + INTO fAllowIn INDICATOR fiAllowIn, + fOkayToBeInBGU INDICATOR fiOkayToBeInBGU, + fKeepStaffOutBGURecNo INDICATOR fiKeepStaffOutBGURecNo + FROM KeepStaffOutBGU + WHERE ForceOut = .fForceOut >> Charles: The variable name "fKeepStaffOutBGURecNo" exceeds the R:Base limitation of eighteen characters, and is probably causing the SELECT statement to fail. Presumabely your're seeing the value in the other variables that you initialized elsewhere. -- Larry
