|
| [WD19] - WDSetup (Custom) bug - WDMOD190.dll |
| Iniciado por guest, 27,ago. 2015 03:08 - 3 respuestas |
| |
| | | |
|
| |
| Publicado el 27,agosto 2015 - 03:08 |
Hi
There are a number of posts on the French forum from August 2104 onwards (re V19) - that describe the issue.
The issue is that a customized WDSetup fails looking for WDMOD190.dll.
There is some indication that this is fixed in the "next" version (version 20 is not a option for me at the moment)
There is also a post on a "workaround" showing French code (see below). Even translating French/English code - the code does not appear identical.
Has anyone experienced this issue and perhaps know of a workaround for WD19 (English). Perhaps WDSetup is working if hfsql files are not being installed on the HF Server (?). I'm also curious as to why no one else has noted this issue on (this) English forum.
Any Help greatly appreciated. (M'Aidez  )
Thanks & Regards
Derek
Posté le 07 novembre 2014 - 10:32
Oui JP, j'avais vu aussi sur ce forum.
NB : idem dans la procédure WDCompo_AfficheTableModif(), on retrouve gclModif.bFichierAModifier(nFic).
J'ai supprimé ces boucles 'TANTQUE PAS gclModif.bFichierAModifier(nFic)', et cela refonctionne ! |
| |
| |
| | | |
|
| | |
| |
| Publicado el 27,agosto 2015 - 07:17 |
Hi Derek,
some years ago I cared a lot for WDSETUP but besides the fact of numerous funnies and bugs and constant fighting with Tech Support I had to realize that I'd have to re-translate the whole thing to German each and every year. Takes a full day of real work. Adding a third language to WDSETUP is quite a pain in the .. too, so just translate the English part - which requires to have the whole project basically in English and not in German! Since then I'm using Inno Setup which is free and does everything what WDSETUP is doing and much more. It sports separate language files(!) in about two dozen languages, it takes 10 seconds to use an other language. Automatic restructuring is not a problem since the arrival of the HModifyStructure() function. With Inno Setup, the signing of the setup file is possible too. Therefore, I will not search for or find any bugs in WDSETUP any more ... |
| |
| |
| | | |
|
| | |
| |
| Publicado el 28,agosto 2015 - 03:05 |
Hi Guenter
Thanks for the advice.
I was/am still unsure which way to jump. Inno will have a learning curve, but preliminary testing with the WDSETUP Project (28000 lines of code, 1500 processes) is proving to be a non-trivial exercise.
This is a bit disappointing. There are only so many days in life, and I had not planned on spending many of them just for an install program.
I can actually get the default installer to do everything that I need at the moment. The main problem being the WinDev badging, and explaining to English speakers what "terminé" means (English speakers are sometimes obtuse, and their heads spin if thy see an non-English word )
Likely I'll have to live with the default installer for a while - and get up-to-speed with Inno when/if I ever have enough time.
Just one further question though. Will Inno handle loading encrypted data files to HFSQL server?
Thanks for your time.
Regards,
Derek |
| |
| |
| | | |
|
| | |
| |
| Publicado el 28,agosto 2015 - 07:39 |
"Just one further question though. Will Inno handle loading encrypted data files to HFSQL server?"
Hi Derek,
no, but you should be able to write a small standalone-program which does the job. Inno Setup is able to run any number of programs before or after doing the install of the main program. In fact, we've been able to do everything by using Inno Setup what InstallShield does - but only for Windows setups. |
| |
| |
| | | |
|
| | | | |
| | |
|