en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en nl en en en ru en en en de en en en en en nl en en en ru en en en en en en en en nl en en en en en en en en en fr en da en en en en en en en nl en en en en en en en en en en en nl en en en en en en en en fr en da en en en en de en en en fr en en en en en en en en en pt en en en en en en
By logging into your account, you agree to our Privacy Policy, personal data processing and storage practices as described therein.
Forgot password or user name?
Search in titles only Search in PowerBASIC for Windows only
You are not logged in. You can browse in the PowerBASIC Community, but you must click Login (top right) before you can post. If this is your first visit, check out the FAQ or Sign Up.
All Time Today Last Week Last Month
All Discussions only Photos only Videos only Links only Polls only Events only
Join Date: Sep 2004
Using Dll's - Solved
30 Aug 2009, 02:21 PM
In order to allow for new reports to be added to an application later I need to be able to call functions within dll's that are not known about at compile time. I am not sure how to link to these dll's at runtime or if this is possible.
Last edited by John Messingham; 30 Aug 2009, 02:41 PM. Reason: Found Answer
Join Date: Sep 2004
30 Aug 2009, 02:40 PM
Using Dll's - solved
The phrase I was trying to remember was 'loadlibrary'
Join Date: Aug 1998
31 Aug 2009, 09:14 AM
In order to allow for new reports to be added to an application later I need to be able to call functions within dll's that are not known about at compile time.
The Provider Payment Partner (tm) System uses this same method to offer not only updated versions of 'standard' reports, but allows users to install custom reports and still be able to upgrade the standard product.
That I did because when I was a user, I was always upset that when the publisher had an upgrade, we had to pay to 're-tailor' our applications.
It's also used in The EDI Pal(tm) ANSI EDI Viewer-Editor-Printer to allow for the separate purchase of licenses for priced add-ons.
Here I had to do that because some users are in healthcare and others in manufacturing/distribution, and would never order both sets of options.
Port Washington WI USA
Join Date: May 2008
31 Aug 2009, 09:33 AM
The approach is also documented in Help, under the topic:
Join Date: Aug 1998
31 Aug 2009, 09:47 AM
Another circumstance in which I use LoadLibrary/CALL DWORD rather than DECLARE is when I am creating/modifiying a function to be stored in a DLL and getting to the point where the new function is to be tested takes a lot of time, eg to go through a logon screen, do a File/Open, etc.
With dynamic loading you can set up the calling program pretty much at the point where you click the button to make the call.
If you have made an error, you can recompile the DLL without a "destination write error [file in use]" and try again without ending and restarting the EXE.
Port Washington WI USA
Copyright © 1998-2022 PowerBASIC Tools, LLC - All Rights Reserved.
Powered by vBulletin® Version 5.7.0
Copyright © 2022 vBulletin Solutions, Inc. All rights reserved.
All times are GMT-5. This page was generated at 05:13 AM.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, and to analyze site activity. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.