Maybe it's a bug but I'm pretty sure that it's triggerd by excessive use of ALLTRIM() in WHERE clause. In the properly design system the lenght of the same key field in the different table is the same. You shouldn't need ALLTRIM() at all. Using alltrim also disables Rushmore optimization of queries and casues other side effects. Also why don't you use cursor instead of temp. table?

SELECT Receive_Note.Receive_Note_ID AS Note_ID, ;
	Receive_Note.Receive_Note_Date As Note_Date,  ;
	Suppliers.Supplier_Name As Factory_Name, Receive_Note.PO_No, ;
	Receive_Item.Product_ID, Products.Product_Name, ;
	Receive_Item.Quantity, Receive_Item.Price, Receive_Item.Amount, ;
	Receive_Note.Total_Amount, 000000 AS Total_Page, ;
	Users.User_Name As Response_Person ;
From Receive_Note, Receive_item, Products, Suppliers, System!Users;
WHERE Receive_Note.Receive_Note_ID == Receive_Item.Receive_Note_ID) ;
		AND Receive_Item.Product_ID == Products.Product_ID) ;
		AND Receive_Note.Supplier_ID == suppliers.Supplier_ID) ;
		AND Users.User_ID == Receive_Note.Receive_Person) ;
		AND Receive_Note.Receive_Note_ID = lsNote_ID);
Into CURSOR myCursor

To make your query easier to read you may consider rewriting it using JOIN clause.

>Hi, All
>
>I was trying to run my old program in VFP 8.0beta. I found one form always reported "Table has no index order set" error, while I running in VFP7.0 without any error message. That's why? The select command of following code is the erorr located. And all the table has index set. Is that a bug of VFp 8.0 or some new rules I didn't got known.
< snip >