>However, the problem was that VFP attached the parent's CDX() file to the resultant set i.e CDX(1, 'cCursor') returned the path to the parent's .CDX, as I have mentioned before, although the cursor has NO index at all! This does not happen with any other table. As a result, following this piece of code, I have a BEGIN TRANSACTION statement which always returned an error (1548), which is, that we cannot have an .IDX file open in a transaction. I know for a fact that there are no .IDX files attached to any of my tables. It seems that VFP is making a temporary .IDX file which points to the parent's CDX() (for optimization maybe) even though you have not asked for one, ONLY if one of the TAGs in the .CDX of the parent table is indexed on a raw DATE field! (DTOS(dDate)) is OK!!
>
>I have checked this out with other tables and it seems consistent. The problem is sorted, but I am a bit confused. Please let me know if you find the same behaviour.

Hi Sanjay - I tested this with a DATE field, and had no problem such as yours...I don't think that's the problem, or it would have caused a lot more trouble for many of us before now...