I see that and agree but two questions:
1.) I copy the PG results to PRIV.  But to display in a form it would be
easier if I had indexes on the PRIV tables, or I just do sub-query for
the children separately I guess?

2.) I was trying to get to a hybrid stage quickly so that if Microsoft
forces me off SMB1 I have a viable option.  It's going to take a lot of
work to move all the logic to PG and I'm afraid I will run out of time.
 This also gives me a chance to learn as I go and work on small chunks
at a time.

3.) OK I lied about the number of questions.  Do you suggest using
tcursors on PG server tables at all?  They seem to work just fine.

Thanks so much for your help.

On 3/11/2020 8:26 PM, Tom Krieg wrote:
> Another reason to always keep all the database processing and retrieving
> logic on the PG server. Rather than link to a PG table in your form, do
> a pass-through PG SELECT .... FROM <table> and link to the result table.
> 
> You're going to spend a lot of unfruitful time trying to get direct
> linking working and when you finally separate Paradox and Postgres with
> pass-through SQL that time will have been wasted. Grit your teeth and
> separate the two now. You'll be glad you did. Performance for one.
> 
> On 12/03/2020 10:21 am, Mark Bannister wrote:
>> It looks likes pdox cannot use an index that has uses the lower function
>> in it.  You get a "number out of range" error and if you look at the
>> table in the filter dialog the index field names are missing on those
>> fields.
>>
>> -- 
>> Mark B
>>
>