Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Active x - Modal/Modeless??

Status
Not open for further replies.

bpratl

Programmer
Jul 7, 2002
25
US
We have a order entry form with a Active X spellchecker control, for a note field, which works fine until we added a Sales Histroy form to display past order data. The form pops up when Icon is clicked. The problem is if the History forms Windowtype is set to Modeless the spellchecker field is disabled. We can only edit if the History form is MODAL.
 
Have you checked the properties of the activeX control for anything that could influence it?


Best Regards,
Scott

"Everything should be made as simple as possible, and no simpler."[hammer]
 
Scott,
There is nothing abnormal in the Active X Spellchecker properties.
Bob
 

Bpratl,

Can you clarify. Does the History form have its own spellchecker button? Or, are you saying that the spellchecker button in the order entry form gets disabled just because you open the history form?

And what do you mean by the "spellchecker field"? Is this the Notes field that you are spellchecking, or what?

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk
 
Mike,
The History form (modeless) is displayed when clicking on one of the three last invoice numbers,which show up on the order entry form (modeless). The labor edit box is a Chado Spelltext Active X edit window. After reviewing sales history(read only)
and releasing the history form, the Edit box is disabled until you release entry form and reopen.
Bob
 
Bob,

So the ActiveX control is the actual edit box that you type into? And it's that that's being disabled?

What you describe is not normal behaviour for an ActiveX control. I'd start by checking dual-interface support, although that's not likely to be the culprit. Try putting SYS(2333,0) in the form's Load, and SYS(2333,1) in the Unload. If that doesn't solve it (and I don't think it will), remove those lines.

Apart from that, I think you'll have to look for the answer from the makers of the control, as it the problem seems to be specific to them.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top