GKK is my company name as I am an independent contractor doing SAP work. GKK actually came from 'Greg Kim Katie' - my family; had to have a name so that worked for me. :)

As for the code I believe I gave you the full package to build it (editors only). I also have some other tools -- my own project manager replacement that integrates the editors and a comparison editor for SCX, VCX, PRG, DBC (structures), and DBF (structures). The editors uses an ActiveX component that I have rights to with source code -- it is CodeMax which has long been a dead product and no longer supported. I have made minor enhancements to it for my uses but I am not a strong C++ developer so any development there has been minimal. You are welcome to use the editor code any way you like. I originally started the editors because I disliked the VFP built-in editors and knew with no further development they were not going to be improved. I had some help along the way from the MS developers for VFP in understanding some of the internal behavior of the SCX and VCX some years back via contacts from VFP User Groups (since I travel a lot I have been able to attend different user groups in the past) that knew the developers directly. Back when I selected CodeMax as the base for the editor component it was the most advanced that I could find and with a syntax highlight engine that was very definable. The developer of CodeMax was actually also an employee of MS and did it on the side, but he eventually decided to end the support and future development; but he gave me full rights to it to use in any way, I don't own it.

Some years back I tried to see if the VFP community was interested -- there was some but no real takers to use them. I believe there is fear of corruption of a VCX or SCX if the GKK editor screwed up which I understand would be a concern. I have actually had VFP do more corruption of my SCX or VCX than my editors which I have been using since around 2006 timeframe (not really sure of the exact year that I started). One of my design decisions of the editors is to use a cursor to hold all the changes being made and then only write back to the SCX or VCX when the user selects save. I felt that this would protect any failures the best. I also create backup of the SCX or VCX before save (or optionally it can be turned off which I do). Another VFP editor function is that it actually creates an instance of the SCX or VCX during design time which prevents you from being able to edit a class that is referenced in a SCX at the same time that you are editing the SCX. My editors do not have that limitation. One limitation of my editors is that it does not provide a graphical display of the form or class fully. I say fully, as they will now display a form or class but it is not fully working. I started it but I was not that interested in the feature and since no one else was using the editors I never finished. I generally do the layout with standard VFP editor and then switch to my editors for managing the code and properties.

I have the built APP files that I can send as well if you like -- just let me know. Also, if you are interested in the other tools let me know as well.