Darrin,

My guess is that your problem stems from running the Fetch in the MapBasic
Window. When you do this, the "next" that MapBasic processes is a global
because you are not running a MapBasic program. For each  MapBasic program,
each table has it's own current record number that Fetch Next works off of.
Not so in the MapBasic Window. You are being affected by anything else that
happens while you fetch. Try this example,

   Open a browser for a sample table and have it display a subset of rows
   Do the Fetch First, Fetch Next and print out a value as in Print
   tablename.colname (should be the second row value as you did a first and
   a next)
   Now click on the browser window and hit CTRL + D to redraw (or on the
   menu, Window /Redraw Window)
   Execute a Fetch Next and print out a value again. The value will be the
   row after the last displayed row in the browser

Basically, the redraw of the browser affected the current row.

The MapBasic window was not designed to do these operations.

Eric Blasenheim
Software Architect
MapInfo Corporation



Mail List:
      [EMAIL PROTECTED]
                                                                  
 From:      on 06/03/2002 01:40 PM AST                            
                                                                  
                                                                  
 To:       "Mapinfo-L" <[EMAIL PROTECTED]>        
                                                                  
 cc:                                                              
                                                                  
 Subject:  MI-L fetch next is skipping records                    
                                                                  



Sorry - This is a follow-up to this morning's question.  It
turns out that what is actually happening is that the [fetch
next] command seems to skip records.  It happens on any
table I use, no matter what the source.  Even an Excel table
we created as a test.  We have packed the table and also
tried indexing on the field we are fetching from (neither
changed the effects).

The MapBasic manual says that certain commands may "reset"
the cursor but that's not what's happening here - it's
skipping records in a very random pattern.

This seems weird.  Anyone have a clue?

Thanks!
*******
Darrin


---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to