>You don't need in this relationships. Actually, the code snippet should look like this:
>*** move record pointer in clients tables (nav button or combo selection)
>nId=clients.id
>Select * From Trips Into Cursor curTrip Where Trips.clientid=nId

Ok, that makes sense.

>This is simplified code, in real situation you better CREATE CURSOR first, e.g. in Form.Init event and just repopulate it when clients pointer moved.

I hate to sound like a two-year-old, but, "Why?" Is there a reason that it's better to create the cursor first instead of just letting the SQL create it?

Thanks,

-Michelle