>Which is one of the big problems with ProMatrix IMHO. The data dictionary PM uses is not even in the same league as DBCx.
>
>>>We currently use VPM 5.0c framework & and are considering purchasing the Stonefield Database Toolkit. Do these two products work well together?
>>
>>VPM has it's own datadictinary that much of it's functionality is tied to. So, getting SDT may not be the best idea.
>>
>>BOb
John,

of course if VPM used dBCX, it would not have worked, because dBCX was too slow for the kinds of direct access VPM depends on. dBCX2 is apparently faster, but it's not faster than a straight SEEK. Of course I understand the limitations in terms of extensibility. VPM's data dictionary is extensible, but not, as you say, in the same league as the new VFE, when it is released. On the other side, the VPM DD has to hold additional information, which could be held in DBCX of course, that is held in the DBC is one is using VFP's RI engine. Having a data structure makes this more comprehensible, IMHO, just as Elie's use of separate tables in xCase makes for a more comprehensible data structure than if he had put everything into one DBCX file.

Anyway, several developers use SDT with VPM, gaining SDT's ability to fix broken data and update changes to data structure. Typically they do their work in SDT, and then work the changes into VPM. Another possibility is to work in xcase, use my importing tool into VPM, and use Doug's importing tool into SDT.

Hank