Joel Break this command down to its barest essentials and see if it works without error:
CHOOSE vchoice FROM #VALUES FOR Stu_Lname ,Stu_Number FROM StudentMaster WHERE Stu_status = 'Student' CAPTION 'Choose Student' LINES 10 FORMATTED If that works OK, start adding one piece back in at a time until you see when it hits the "wall" If it doesn't work, SELECT COUNT(*) from StudentMaster where Stu_status = 'Student' How many rows are being returned? Try adding another condition to limit the rows further and see if that helps. David David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: "Joel Solomon" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Monday, May 23, 2005 1:08 PM Subject: [RBG7-L] - RE: Memory allocation > Dave, > > The indexes are OK and the form is not corrupt. In fact, I am having the > same problem with the following choose statement. I set up the choose > command this way so the columns in the choose box are uniform. > > CHOOSE vchoice FROM #VALUES FOR ((LJS(Stu_Lname,20)) + (LJS(Stu_Fname,20)) > + (Stu_Location)) ,Stu_Number FROM StudentMaster ORDER BY Stu_Identify WHERE > Stu_status = 'Student' CAPTION 'Choose Student' LINES 10 FORMATTED > > Joel > > ----- Original Message ----- > From: "David M. Blocker" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[email protected]> > Sent: Monday, May 23, 2005 12:57 PM > Subject: [RBG7-L] - RE: Memory allocation > > > > Try rebuilding the indexes > > > > 1. Backup the database > > 1. DISCONNECT > > 2. Backup the database > > 3. SET MULTI OFF > > 4. CONNECT database > > 5. PACK KEYS > > > > If that doesn't help, consider the possibility that the form is corrupted. > > Try creating a new one with JUST that lookup expression - does it work? > > > > David Blocker > > [EMAIL PROTECTED] > > 781-784-1919 > > Fax: 781-784-1860 > > Cell: 339-206-0261 > > ----- Original Message ----- > > From: "Joel Solomon" <[EMAIL PROTECTED]> > > To: "RBG7-L Mailing List" <[email protected]> > > Sent: Monday, May 23, 2005 12:29 PM > > Subject: [RBG7-L] - RE: Memory allocation > > > > > > > Paula, > > > > > > Yes they are. > > > Any other ideas of where I might look for this problem? > > > > > > Thanks > > > Joel > > > ----- Original Message ----- > > > From: "Paula Stuart" <[EMAIL PROTECTED]> > > > To: "RBG7-L Mailing List" <[email protected]> > > > Sent: Monday, May 23, 2005 11:57 AM > > > Subject: [RBG7-L] - RE: Memory allocation > > > > > > > > > > Joel, > > > > > > > > I've got similar selections running in forms against a database > > > > of 300,000 records using XP Pro with 512 MB memory with no problems. > > > > Are the lookup columns indexed? > > > > > > > > Paula > > > > > > > > -----Original Message----- > > > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Joel > > > > Solomon > > > > Sent: Monday, May 23, 2005 11:46 AM > > > > To: RBG7-L Mailing List > > > > Subject: [RBG7-L] - Memory allocation > > > > > > > > > > > > Good Morning, > > > > > > > > I would like to know if anyone has run into this problem. I get an > > > > error in my form lookup that states that I do not have enough memory > to > > > > allocate to the lookup function. I have only 1,200 records and I am > > > > using a multi-column lookup using 3 text columns. My computer has 512 > > > > MB of memory and I am running Windows XP. When I change the > > > > mulit-column lookup to 2 text columns, the error goes away. > > > > > > > > Short of increasing my memory, what else can I do? I find it quite > > > > strange that 1,200 records would cause this kind of problem. > > > > > > > > Thanks > > > > Joel Solomon > > > > V.P. Finance > > > > Barbizon International > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > >
