baanguy2
15th September 2014, 23:55
Hi,
We had a working Qkey (with Baan 4c4) and after the porting set upgrade qkey stopped working, anybody has been thru this experience and how did u solve the issue, that would help us a lot.
Thank you,
GaryEd
16th September 2014, 15:58
Might help if you told us which porting set you upgraded from and to.
mark_h
16th September 2014, 16:28
And see the post by Joy - http://www.baanboard.com/baanboard/showthread.php?t=66828
Joy Conner
17th October 2014, 23:45
What porting set did you upgrade to? using SLM?
Joy Conner
17th October 2014, 23:46
I forgot you need to install qkey after porting set change
ben.kansas
17th November 2014, 17:21
Interesting! I thought QKey was a defunct product. Is it still being maintained or are you using it without support?
mark_h
17th November 2014, 18:09
We are using without support as far as I know. We just install it again after a upgrade or something like that. So far it keeps working - but we are still on 4c4.
Joy Conner
17th November 2014, 19:53
We use Qkey on Windows OS without fullscope support. Next year we will set up porting set with SLM and test qkey. I have read RedKlay material stating that you can define the object within Qkey script. Will test this and report the outcome.