Thankyou for your time - My path is:
<!-- #include file = "CuteEditor_Files/CuteEditor_Files/include_CuteEditor.asp" -->
If this path is in correct the page will not render (include file not found). The path I an using is correct, the page renders error free, the editor shows as it should, all the editor tools work as they should, the spell (NetSpell) works like a wet dream. Mate we are so close to getting this system (a briefing system for the Australian Defence force) past the dev phase into a preliminary live environment its not funny, they love it in its dev environment (XP stand alone)!!!
I have it working great on my XP pro machine (classic ASP app) They have all but signed off on it. My self and my company (
www.framegroup.com.au) will be out of flavour if I can not resolve this issue asap. The benefits to your product will be massive if this editor gets the green flag. The reason yours will get the nod - NO client side dependencies what so ever. They have a strict NT workstation SOE and a strict 2000 Server (the intended live environment where I a having trouble) SOE all other products I have tested need text files on the client or to execute some .exe to get a spell checker working.
This morning I went direct to the box and got clearence to copy the files directly, the problem still exists. What I was mentioning in my previous post about spliting the files and sweing them back to gether please dis regard.
BTW : When I click the Preview or HTML buttons not only do I get the error talked about above, the mode does not change. I can not view the HTML at all. Also when I submit the page, no data is found in the editor form variable. No matter what I type inside the editor an empty string gets posted. As I said this is happening in your test editors also.
Whats the chances I can call you. We will pay for your time, where are you in the world. If this gets fixed you will sell many instances, they will probably purchase the source code and enter into an open agreement.
TYIA
Wind is your friend