I've noticed strange behavior with the REPLACE and have been wondering if there is an explanation for it. Here it is:
1. view1, a remote view, is SELECTED
2. then a stored procedure executes to create cursor1 -
of course cursor1 is automatically selected after the sp
3. a message pops up if cursor1 is empty
4. then a REPLACE view1.field1 occurs
The REPLACE works fine and dandy when cursor1 has records. If it doesn't, the REPLACE is skipped - and there's no code to skip it. The problem seems to be that cursor1 is at EOF, and the only way for the REPLACE in view1 to work is to first SELECT view1 even though the REPLACE has the view1 reference on the field. Easy to get around, but just wondering if there's a logical reason. Thanks.