Hi Kevin

Clarification requested: "putting all methods needed in the uses block"

You are referring to the Uses block within the library and listing its methods
accordingly in the uses block?

Regards

Jeremy.

"Kevin Zawicki" <numberjack@wi.rr.com> wrote:
>
>I think you are running into the uses declare the library and not each method
>compile issue. I (and others have written quite a bit about this).
>
>You are better off putting all methods needed in the uses block. It is more
>stable and avoids the circular reference.
>Also try to have unique method names throughout all forms and libraries.
>
>Some posts...
>
>http://pnews.thedbcommunity.com/cgi-bin/dnewsweb?cmd=article&group=pnews.paradox-programming&item=32444&utag=
>
>http://pnews.thedbcommunity.com/cgi-bin/dnewsweb?cmd=article&group=pnews.paradox-programming&item=38026&utag=
>
>
>
>"Jeremy Stagg" <jeremy.stagg@itsysadmin.com.au> wrote:
>>
>>Having an issue withthe simple delivery of a library (lsl -> ldl) and the
>>resulting compiler warning of:
>>"this file does not have any symbol table information".
>>This happens when referring to a delivered library from the main form,
and
>>the library is referred to in the "Uses" list
>>of libraries.
>>Source library files (lsl) work fine.
>>Any tips as there about 1 paragraph I can find that relates to symboltable
>>in ObjectPAL, otherwise down a Delphi rabbit hole.
>>Cheers
>>Jeremy.
>