Bill,
Can we guess that in select ... into is a simple alias for
selection that is a unique table? If you use into, selection as a table
name is not available anymore (even if selectioninfo() is). I guess that as
result exists as a distinct table only when committed, if not it
Hi Bill,
You've entered the twilight zone (i) - of undefined default behaviours, I
fear. :-)
No, it's really a question of what the cursor is set to when you haven't set it. If
you add a Fetch First ... before each column
reference (Print statements), or at least before the last
On Sun, 1 Aug 2004, Lars V. Nielsen (GisPro) wrote:
But the example proves that selection tables doesn't have their own
cursor, it's using the cursor of the base table. Which makes sense,
since a selection table isn't really a table technically, it only works
that way in a logically sense.
