Environment versions
Network:
Windows Server 2012 R2
>>This would query the base record source twice into 2 cursors, if I interpret you correctly (also changing alias of created cursor).
>
>1 CAD class (original),
>1 sub-class with a slightly different .selectCmd (can be set at design time or in .Init()) and a different .Alias
Yupp, as I thought. I still think querying the cursor given from original CAD to be better architecture and probably better performant if indexed binary, as it is a sub-set already clearly established - your worst case: large source table filtered to rights of user and/or area (or "Bag" multipurpose table sometimes used in the nineties to save file handles), where most of records have to be filtered out using dbf over LAN/WAN.
Drawback factor: time to index BINARY on client plus added minimal refresh/update time due to automatic re-indexing. Should not be a problem if cursor reccount is within 4 or 5 digits.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only