DBF Viewer 2000 - changing table structure?

[BlackDice]

I'm wondering if anyone else has used DBF Viewer 2000 and had any adverse effects. We've used this application to view tables at a client site, and for some reason a simple query such as:

Select * from tblPerson WHERE personid = 3

doesn't return any records, even though I can open the table and look right at the record, or use the command window to print out the current value of personid when I'm on a record, and it returns 3 (which is correct). If I take the table and perform a SELECT INTO TABLE command, then run the query on the new table, everything runs just great. This only happens to the table after using the above mentioned application to view it. Has anyone seen this or know what's going on?

BlackDice

http://www.stillwaterexpress.com

 

[TamarGranor]

I don't know DBF Viewer 2000, but you may be running into the situation where VFP pulls a fast one. When a query INTO CURSOR involves a single table, has only actual fields from that table in the field list and is fully optimizable, VFP filters the original table rather than creating a separate file. Try adding the NOFILTER keyword to the query and see if that fixes it.

Tamar