Interesting bug/feature

[Michael]

Preliminary testing suggests that, in a procedure, a Select command  
which selects an empty set will invalidate all subsequent field- 
related commands (until a non-empty set is selected) but will allow  
Print (and perhaps other) commands.

For example,

SelectA = ""		; where A has no null values
Fill B "hello"
Print ""

will not fill field B but will print the database.  If, however,  
SelectAll is inserted after the first line, all is well.  I know that  
it is poor programming to omit the SelectAll command but it is  
possible to do so and, more importantly, its omission can generate a  
quite baffling error.  It appears that an empty result of a select  
command has the effect of the rest of the procedure operating on an  
empty database.

michael