Leaderboard

There is another subforum for announcements and information about third-party packages: https://en.delphipraxis.net/forum/13-delphi-third-party/

Six new zips for Win32 and Win64 versions of OpenSSL 1.1.1d, 1.1.0l and 1.0.2t can now be downloadable from the Wiki at: http://wiki.overbyte.eu/wiki/index.php/ICS_Download or https://www.magsys.co.uk/delphi/magics.asp . The latest 1.1.1 DLLs are also included in the ICS distribution SVN and overnight zip. These releases include four low priority security improvements and bug fixes, including a Windows specific fix where configuration files placed in 'C:/usr/local' could override some OpenSSL settings. ICS applications require V8.57 or later to support OpenSSL 1.1.1c. Changes in 1.1.1d may be found at https://www.openssl.org/news/openssl-1.1.1-notes.html , 1.1.0l may be found at https://www.openssl.org/news/openssl-1.1.0-notes.html and 1.0.2t at https://www.openssl.org/news/openssl-1.0.2-notes.html Angus

Hi Alexander, OK. If I remove the Close in the procedure TCurrentCustJobsForm.btnSelectClick(Sender: TObject); Then it works OK. After some playing around I ended up with the following.. In CurrentCustJobsForm: procedure TCurrentCustJobsForm.FormClose(Sender: TObject; var Action: TCloseAction); begin Action := caFree; end; No Select or Close button action. Select has ModalResult of mrOk & Close button has mrClose. In the calling form I have.. procedure TJobTicketsForm.ShowallJTsforthecurrentJTCustomer1Click(Sender: TObject); var iRecord: Integer; begin if TCurrentCustJobsForm.Execute(iRecord) then if iRecord <> 0 then dmC.JobTickets.Locate('JobNo', iRecord, []); end; All good now. I learnt some things about various interactions here. Regards & Tks, Ian

I use the policy that all projects must be completely self-contained. Each project has a complete copy (source and installer) of the all the in-house and third party libraries used. The project search path points to the local copies. I always build from the source. dcu, exe and bpl files goes into local project folders. Everything is under version control. Getting a project setup on a new system is just a matter of fetching the project from version control, running any necessary 3rd party installers (usually just for design time functionality) and installing the bpls. Since the different projects tend to use the same libraries the two last steps are usually just done once. I don't care about what the installers do because I don't use their dcu-files or their search paths. The project itself contains it all. Never had problems with duplicate dcus (since I started doing it this way, that is). There's of course the problem that different projects might use different versions of design-time components, but that is a bit outside the scope of your question. WRT the VM solution I used it a while ago and it actually worked very well. I used Hyper-V with one VM per project. The only problem was that it got a bit tiresome to have to install the same tools in each and every VM whenever there was a change in the toolset.

*puts sunglasses on and holds a pen up*