C
Clinton
Hi there
Sorry for bothering you, but after weeks of scouring the net, I came across
the following entry which you solved:
http://groups.google.com/groups?hl=...s_miny=2003&as_maxd=12&as_maxm=4&as_maxy=2004
The solution worked for me as well! However, I'm trying to obtain some
background info on why Office 2003 caused this problem in the first place?
The person you were helping said that his application would just modify this
registry entry so as to allow the control to run. Surely this is just a
workaround? What was the reason for this Compatibility entry being set with
400 in the first place?
Surely every developer around the world is not expected to modify this
registry entry to allow the VB6 Rich TextBox Control 6 SP4 to work after
Office 2003 has been installed?
(Really!) looking forward to your reply.
Kind regards
Clinton
Sorry for bothering you, but after weeks of scouring the net, I came across
the following entry which you solved:
http://groups.google.com/groups?hl=...s_miny=2003&as_maxd=12&as_maxm=4&as_maxy=2004
The solution worked for me as well! However, I'm trying to obtain some
background info on why Office 2003 caused this problem in the first place?
The person you were helping said that his application would just modify this
registry entry so as to allow the control to run. Surely this is just a
workaround? What was the reason for this Compatibility entry being set with
400 in the first place?
Surely every developer around the world is not expected to modify this
registry entry to allow the VB6 Rich TextBox Control 6 SP4 to work after
Office 2003 has been installed?
(Really!) looking forward to your reply.
Kind regards
Clinton