Hi Alex,

tnDSID defaults to the current datasession. This gives the ability for callers from any datasession to call this routine, which uses a class, and get the table/cursor opened in the specified datasession.

And yes, tlLoud means it lets the user know what's happening.

I do a lot of this kind of packaging: it makes code more intelligible, with less typing, and less temptation to cut corners. Also the routines get proven and improved over time. That I could open a table from outside the exe was just a bonus. :)

Hank

>>>In several places in our application executable we have hooks that call custom, external, encrypted programs whose names are stored in a table.
>>>
>>>Recently, a new custom program needed to USE a confidential free table that is included in the executable, and VFP couldn't find it.
>>>
>>>Is there any way that we can force the external program to look for the table inside the exe file?
>>>
>>>TIA,
>>>
>>>Alex
>>
>>Hi Alex,
>>
>>I have a prg, usetable, which takes the following parameters:
>>
>>LPARAMETERS tcTable, tcAlias, tcDir, tlExclusive, tnDSID, tlNoUpdate, tlLoud, tlUseDD
>>
>>There is no execscript or macroing involved, for the reasons others have cited.
>>
>>Mine is geared toward my particular usage requirements, but you get the idea.
>>
>>hth,
>>
>>Hank
>
>Thank you for the suggestion Hank.
>
>I can figure out most of the parameters except tnDSID and tlLoud. (Is tlLoud something like Verbose or Notify? )
>
>LPARAMETERS tcTable, tcAlias, tcDir, tlExclusive, tnDSID, tlNoUpdate, tlLoud, tlUseDD
>
>Alex