>I actually need the transaction to be the parent and the customer to be the child (so when the transaction is selected, the pointer in the customer table is sitting on the right record). I know I can do it with a view, but can't it be done with a table to table relationship? and again, which would be more beneficial?
>
For a relationship:
Just set the relationship the other way, e.g.
USE customer ORDER id
SELECT 0
USE transactions
SET RELATION TO customer_id INTO customer
I prefer a view or a SELECT statement, which would bring the info together in one cursor.
Insanity: Doing the same thing over and over and expecting different results.
