Earlier in this thread and in another thread you reported this error:

2065
Table "C:\DOCUME~1\swill001\LOCALS~1\Temp\00003IMX00J7.TMP" has a file length / record count inconsistency. The table will need to be repaired before transactions can be committed properly.
C:\DOCUME~1\swill001\LOCALS~1\Temp\00003IMX00J7.TMP

You seemed to be saying that you thought the 2065 error was fixed in VFP 9 SP1, however I have looked over the fix list for SP1 and see nothing related to the 2065 error. I am wondering about your results in squashing this error.

Also, in relation to the "Cannot insert an empty row from a view or CursorAdapter into its base table(s)" error that you reported, I find that this is a corrupted view. Specifically, if you run GenDBC, you will most likely see that the tables that are set to be updateable for the view in question contain a table that should not be there. For instance, if you have a simple two table view and one table is going to be updated and one is included because you're pulling some data from it, then the table list should only contain the first table. The second table will not be there, but sometimes VFP fouls it up and it includes the second table in the list. Remove the second table from the list and the problem should go away.


>Can you please give me more information about the problem? Basically, I don't have problems with CA except for some strange sporadic error "Cannot insert an empty row from a view or CursorAdapter into its base table(s)." It happens once in a while and I was not able to reproduce it yet or do something about it. Other than that I don't have any problems with CA using Mark McCasland's CA builder. We're not using grids for input.