>>I found in the SDT.VCX where the table SDTMeta and SDTUser is opened (USE command). Now I am wondering, how I can prevent getting (rarely but still sometimes) a message "cannot read SDTUSER.CDX or SDTMETA.CDX".
>
>Rather than trying to prevent the message, I'd try to fix the problem. You can build those tables into the EXE since they shouldn't change at runtime.
>
>Doug
Hi Doug,
If I may ask you another question, please. SDTUser.dbf is straight forward; it looks like the same file in many of my folders. But the SDTMeta.dbf is different (size and date stamp); even though I never remember changing it.
How would you recommend choosing which SDTMeta.dbf to include in the EXE?
UPDATE. I found the SDTMeta.dbf in my "main" DATA folder and this is what I will include in the EXE. But I still have two follow-up question, please
1. When I make a change - during design stage - in the VFP database (e.g. add a field or remove a field or remove a DBF from the DBC container), using the SDT, does it change the records in the SDTMeta.dbf?
2. What about tables CoreMeta.dbf and DbcXReg.dbf; can they be included in the EXE as well?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
