Sequential Save add-in - Registry error setting options

  • Thread starter Thread starter Hank Scorpio
  • Start date Start date
H

Hank Scorpio

I've downloaded the Sequential Save add-in from
http://www.mvps.org/skp/seqsave.htm

It's a useful tool, but I've come across one problem; whenever I try
to set the options, the following error appears:

--------------------
Run-Time Error 26001

Failed to delete registry key: -2147483647', Section: Software\Shyam
Pillai\Sequential Save\', Key: Subfolder name
------------------

The error still appears even if I go into RegEdit and create that key
prior to trying to set the options. It also appears whether I've made
any changes to the options, or am just selecting [OK] for the default
ones.

This is happening on four separate machines, two running Windows XP
Pro, one XP Home, and one Windows 98. It seems to be such a widely
used add-in that I was surprised that I didn't find anything in a
Google search about this, but on the other hand the file that I
downloaded was dated only 28-MAY-04 so it could be something relating
to a recent change.

I've e-mailed a copy of this post to Shyam, but on the not
unreasonable assumption that he has a life away from his computer and
may therefore not see it for a while I thought I'd ask the Group
whether they've encountered this problem and /or found a workaround.

Thanks.
 
Hank,
I can reproduce the error only when I have 'Break on all errors' turned on
in the VBE Options dialog. If it is set to 'Break on Unhandled errors' I am
unable to reproduce it. There is an error handler in the routine so I am
wondering if you have turned on the first option?
 
Hank,
I can reproduce the error only when I have 'Break on all errors' turned on
in the VBE Options dialog. If it is set to 'Break on Unhandled errors' I am
unable to reproduce it. There is an error handler in the routine so I am
wondering if you have turned on the first option?
Click to expand...

Shyam,

I'll bet I know what this is. I should have mentioned that where I
work we're cursed with still being on Office 97. The VBE in that
version is stuck with having "Break in class modules" as the default.
You can't change it by code, and changing the setting manually doesn't
persist between sessions. What that means is that whenever you try to
pass an error out of a class module, even if it's handled in the .bas
module (or a form module, or another class module) that called the
class, then the code will break. Passing errors back WITHIN the class
module is OK; it's only when you go to pass it OUT of the module that
you're stuck. It's been the bane of my life when writing Excel tools
in '97 workbooks.The problem was corrected in Office 2000.

When I changed the setting to "Break on Unhandled Errors", it went
away. The problem of course is that that only works in that session.
(On the other hand I suppose that it'd only be necessary to change the
setting for the session that you want to set the options in.)

Regards,

Hank.
 
Back
Top