Some bright spark has suggested that we go to KCML6 and stay with WDW to save the licence costs. ADP tell us that no one else in the world has this setup but that seems to be a of little importance to those interested in saving money.
Has anyone tried KCML6 with WDW and if so were any issues encountered or can you think of any likely problems. I am eager to come up with some way of stopping this lunacy.
I am aware of the Kclient and WDW restrictions you mention.
I know KCML6 is free , I just wanted to be safe and use KClient.
What I am trying to find is some reason that will stop me being the only person on the planet supporting KCML6 and WDW
We ran (still do) with WDW without a problem, just as long as you don't want to use KCML forms.
We actually found that a switch from WDW to Kclient caused more issues as users were used to function keys and macro's that Kclient did not support.
And now the questions ......
Which versions of KCML6 and WDW do you use?
How long have you been running this combination?
I am keen to use ODBC with KLCML6 , do you have experience of that and if so how did you find it?
KCML6 will come with ODBC, never had any issues with that.
We use the sources file for the datasources, there is an issue that if a kconf.xml file exists within the kcml folder then it overrides sources, so delete kconf.xml if you are not using it.
The only issue that you might come up against with KCML6 is that if you are runing Linux, the SHELL functions execute slower for some reason.