SP3 and RefEdit Control

[Bob Flanagan]

Shortly after installing SP3 in Excel 2003, I created a new workbook with a
refedit control on a dialog. At least, I tried to. I got an error message
when I tried to add the refedit control. So I did a repair of Office. I
was able to add the control then. However, when I check Tools, References, I
have a reference to a refedit.dll. And I have to remove it in order to
share the files with others. Otherwise, they get an error in module 1
message. The refedit control works fine after the reference is removed.

Any ideas on how to make the addition of the refedit control work properly
and not add in that reference?

Bob

 

[Jim Cone]

Bob,
Thank you for that information.
I just added a RefEdit to a form in XL2003 (sp 3) and got that same reference added.
I have not seen that before in prior XL versions.
Removing the reference seemed to have no effect in XL2003 on the
operation of the control. Isn't that the case for you?
I develop in XL 2002 using the XL97 help file and try to avoid using
that control if at all possible.
--
Jim Cone
San Francisco, USA
http://www.realezsites.com/bus/primitivesoftware
(Excel Add-ins / Excel Programming)




"Bob Flanagan"
wrote in message
Shortly after installing SP3 in Excel 2003, I created a new workbook with a
refedit control on a dialog. At least, I tried to. I got an error message
when I tried to add the refedit control. So I did a repair of Office. I
was able to add the control then. However, when I check Tools, References, I
have a reference to a refedit.dll. And I have to remove it in order to
share the files with others. Otherwise, they get an error in module 1
message. The refedit control works fine after the reference is removed.

Any ideas on how to make the addition of the refedit control work properly
and not add in that reference?
Bob

 

[Bob Flanagan]

Jim, yes removing the reference seems to have no effect at all. I have gone
back and check workbooks back to June of last year and they have the refedit
control reference in them. Removing it does not cause any error on
subsequent opening and closing of Excel or the workbook.

I did get a report from one user who used a file that had the reference in
it and it worked fine. Then I sent her an update (post SP3) and she had the
problem. I removed the reference and things worked fine. She then went
back to the original pre SP3 modified file and did not get a reference
problem. It is almost as if the problem happens if the file is created or
modified post SP3. Or at least post my repair of Office which I did to fix
a problem caused by SP3.

I'm pretty confused, but I know that several others are posting about this
problem on another forum, so will share what I find from that forum.

Everyone else, please hop in!

Bob

 

[Charles Williams]

I did have one compile error problem that was caused by a reference to
RefEdit in FastExcel, removing the reference seemed to fix it.
We have also been having various problems with the Treeview control just
recently in Name Manager.
Treeview needs a reference to MSCOMCTL.OCX.
We had compile errors, invalid typelib errors ..., but only on some
machines, some with Vista, some with Win XP. Dont know if they were all XL
2003.

In the end we just stopped using Treeview as it was not really that
important, and so far that has fixed the problems.


Charles
__________________________________________________
Outlines for my Sessions at the Australia Excel Users Group
http://www.decisionmodels.com/OZEUC.htm

 

[Jon Peltier]

I had a problem yesterday with some userforms with RefEdits. I'd built the
forms in Excel 2007, probably SP1, but I converted the file to Excel 2003,
and opened it in Excel 2003 SP2 (not SP3), and the RefEdits on the UserForms
were gone. I added a RefEdit to one form, then thought I should check the
references. I had one working reference to RefEdit.dll (presumably the one I
just added), and one MISSING reference to RefEdit.dll (presumably the broken
one).

So I wonder if 2007 SP1 has the same effect as 2003 SP3? I was just going to
ignore this, or attribute it to trying to backsave the workbook, but maybe
that's not the issue.

- Jon

 

[Jon Peltier]

Hmm, no, that wasn't it. I got the error in 2007 when I opened the workbook.
On the computer on which I created the workbook, the dll is in

"c:\program files\microsoft office 2007\office 12\"

but on this computer (actually a virtual machine on this computer), Office
2007 is installed in

"c:\program files\microsoft office\office 12\"

I've never had this issue with a nonstandard installation directory before,
and I'm a bit surprised it came up here.

- Jon