Hi Javier.

>As far as I remember (I did not document this, nor did I report to you, it's my fault), the problem was that if I want to open a certain DBCX in a given lcPath, if there is another DBCX in the set('path'), the DBCX object instantiation takes the DBCX in the set('path') instead of the one that I want to open, even if I put the lcPath explicit in the init call.

I haven't seen that, nor do I understand why it would happen. The only time VFP overrides the path you provide for a file is if you're running in an EXE, the file you specify exists inside the EXE, and you specify a file with the same name outside the EXE. In that case, regardless of the path you specify, VFP always uses the file inside the EXE. However, I'll check the code in DBCXMgr.Init and see if there's something there that may explain this.

>In custom fields and common fields, the data dictionary is heavily used, and user interface, validation, reports, labels, ... rely on it. This is why I have come across very complete scenarios, and what I missed the most are tools to take better advantage of the data dictionary.

Very interesting!

>All in all, as I told you SDT for me is a must for any VFP developer. Thanks again for developing it,

Thanks for the kind words.

Doug