>>>I got most problem if mix all tables in one Form...
>>>Because there relationship are cyclic!!
>>>
>>>Tables:
>>>Customer(Cust_no, ... ) Carry Customer info
>>>Orders(Order_no, ...Cust_no[FK]... ) Carry Each order info
>>>Chooseitem(Order_no,item,....) OrdItems in meaning
>>>Item(ItemKey, ...) Carry item info
>>>Spprice(Cust_no,item, ...)
>>>* Special Price lookup Table for each Customer
>>>
>>>But last table link two tables and form a cyclic relationship....
>>>

>>>                          Spprice>-----------+Item
>>>              _____________\/   +              +
>>>             /                   \________     |
>>>            +                             /\  /|\
>>>     Customer +-------< Orders +-------< Chooseitem
>>>

>>>
>>>As VFP only make One work area, the link on finding will make a loop
>>>and many unexpectly, or empty or multiple will come out on join
>>>table....
>>>
>>>Currently I cut the Spprice Table into another Form to avoid this.
>>>But the problem may happen sometime... ~>.<~
>>>Any suggestion to me?!
>>
>>Don't create cyclic relationships, at least physically.
>
>Of cos, I know... but current Dbase has them...
>It take sometime 5-15mins to find records on printing.... +_+'

Database (if you mean dbc file) can have persistent relationships only (used for RI triggers). All other relationships (temporary) you may or may not set in Form Designer (DE) or programmatically (SET RELATION). Therefore, just be careful not to set cyclic temporary relationships. If it's really necessary to set this kind of relations for printing (which is probably arguable) then you can just SET RELATION right before REPORT FORM and release them after the printing.