Maybe someone else can, but I can't help you without seeing the code prior to file check one and two to see what table is in the current work area and how it got selected. Instead of debugging there, why don't you just select the correct cursor (curlnksheet) when you check the alias() if that check fails? Then set it back afterwards if it has to be set back. Can't help anymore without the code.
Tracy

>The following code is from a debugging portion of code trying to solve an issue. During the process we SCAN a cursor (CursorA), unzip a file or Foxpro tables, create cursor 'CurLnkSheet' from these tables and run the report. The process runs fine for the first record in CursorA, once we move to the next record, file check one passes, but the report is wrong, it prints one detail line for the number of records in CURSORA, and File CHECK TWO fails, showing the current alias to be CURSORA. Needless to say this is driving us nuts!!!
>
>Any help would be appreciated.
>
> lcTFile = "c:\psfiles\psout.ps"
> IF FILE(lcTFile)
> ERASE (lcTFile)
> ENDIF
> *****FILE CHECK ONE ***********
> IF LOWER(ALIAS()) # "curlnksheet"
> SUSPEND
> ENDIF
> REPORT FORM reports\urllinks TO FILE &lcTFile
> ****** FILE CHECK TWO *********
> IF LOWER(ALIAS()) # "curlnksheet"
> WAIT WINDOW ALIAS()
> SUSPEND
> ENDIF