Results 1 to 10 of 10

Thread: Accessing one library from another

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #10
    Join Date
    Jan 2009
    Richmond, VA

    Default Re: Accessing one library from another

    I'm not sure if I'm testing correctly but I just unzipped the latest library from vdfguidance and added it to the Client Web Services workspace (it already uses one library and both are using relative pathing) and then added "Use vWin32fh.pkg" to the top of the src and it compiles fine. The makepaths seem to be as expected...
    C:\DataFlex 19.1 Examples\Web Services Clients\AppSrc
    C:\DataFlex 19.1 Examples\Example Library\AppSrc
    C:\DataFlex 19.1 Examples\vwin32fh   <-- this is for appsrc
    C:\DataFlex 19.1 Examples\Web Services Clients\DdSrc
    C:\DataFlex 19.1 Examples\Web Services Clients\Data
    C:\DataFlex 19.1 Examples\Web Services Clients\Bitmaps
    C:\DataFlex 19.1 Examples\Example Library\Bitmaps
    C:\DataFlex 19.1 Examples\vwin32fh  <-- this is for bitmaps
    C:\Program Files (x86)\DataFlex 19.1\Bin
    C:\Program Files (x86)\DataFlex 19.1\Lib
    C:\Program Files (x86)\DataFlex 19.1\Usr
    C:\Program Files (x86)\DataFlex 19.1\Pkg
    C:\Program Files (x86)\DataFlex 19.1\Bitmaps
    ...I then added the vwin32fh library to the example library and removed it from the web service clients (so now the only path to the package is "through" the example library) and it still compiled fine and the makepaths are exactly the same. So I'm guessing there is something else at play here, not the nonstandard structure of the library.
    Last edited by Stephen W. Meeley; 9-Jul-2018 at 10:25 AM.
    Best regards,


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts