Excel hangs on entry or exit from spreadsheet with macros with new

I have an Excel workbook composed in an Office 2000 system that works
perfectly. It contains various bits of VBA and macro, nothing complicated,
controling how user can insert lines etc., shutting the workbook if there is
no input for 15 minutes(using ontime), hiding different bits of data
depending on a control button.

As I have said it works perfectly until; we are now upgrading to XP and it
does not work at all with that operating system. Sometimes it will load and
then hang when you try to exit and some times it hangs on loading resulting
in the MS "Microsoft has encountered.......etc etc; do you want to send an
error report?" screen.

We have tried REM'ing out all the code in the Workbook Open module but we
still have the same problem/ s Clearly there is somthing that the OS doesn't
like. Has anyone encountered this problem before? and have you any ideas. Our
IT department are stumped!!

regards to all

Malcolm

Malcolm

Are you upgrading to Windows XP or Office XP? There should be no
difference.

I have Office 2003 installed, if you'd like to send me the workbook I'll
give it a test

--
HTH
Nick Hodge
Microsoft MVP - Excel
Southampton, England
nick_hodgeTAKETHISOUT@zen.co.uk.ANDTHIS


"MalcUK" <MalcUK@discussions.microsoft.com> wrote in message
news:0B1760D3-55C3-4CD6-9293-A6A6D18E159A@microsoft.com...
>I have an Excel workbook composed in an Office 2000 system that works
> perfectly. It contains various bits of VBA and macro, nothing complicated,
> controling how user can insert lines etc., shutting the workbook if there
> is
> no input for 15 minutes(using ontime), hiding different bits of data
> depending on a control button.
>
> As I have said it works perfectly until; we are now upgrading to XP and it
> does not work at all with that operating system. Sometimes it will load
> and
> then hang when you try to exit and some times it hangs on loading
> resulting
> in the MS "Microsoft has encountered.......etc etc; do you want to send an
> error report?" screen.
>
> We have tried REM'ing out all the code in the Workbook Open module but we
> still have the same problem/ s Clearly there is somthing that the OS
> doesn't
> like. Has anyone encountered this problem before? and have you any ideas.
> Our
> IT department are stumped!!
>
> regards to all
>
> Malcolm

Hi Nick

Thanks for the reply, sorry for the delay in replying have been away from
the office since last Wednesday. Most of the dept is on 2000 but as new
machines are installed in the office they come with Windows XP operating
system which seems to be having the problem with the spreadsheet. Will send
you the workbook , please don't laugh at me attempts at VBA coding!!

regards

Malc

"Nick Hodge" wrote:

> Malcolm
>
> Are you upgrading to Windows XP or Office XP? There should be no
> difference.
>
> I have Office 2003 installed, if you'd like to send me the workbook I'll
> give it a test
>
> --
> HTH
> Nick Hodge
> Microsoft MVP - Excel
> Southampton, England
> nick_hodgeTAKETHISOUT@zen.co.uk.ANDTHIS
>
>
> "MalcUK" <MalcUK@discussions.microsoft.com> wrote in message
> news:0B1760D3-55C3-4CD6-9293-A6A6D18E159A@microsoft.com...
> >I have an Excel workbook composed in an Office 2000 system that works
> > perfectly. It contains various bits of VBA and macro, nothing complicated,
> > controling how user can insert lines etc., shutting the workbook if there
> > is
> > no input for 15 minutes(using ontime), hiding different bits of data
> > depending on a control button.
> >
> > As I have said it works perfectly until; we are now upgrading to XP and it
> > does not work at all with that operating system. Sometimes it will load
> > and
> > then hang when you try to exit and some times it hangs on loading
> > resulting
> > in the MS "Microsoft has encountered.......etc etc; do you want to send an
> > error report?" screen.
> >
> > We have tried REM'ing out all the code in the Workbook Open module but we
> > still have the same problem/ s Clearly there is somthing that the OS
> > doesn't
> > like. Has anyone encountered this problem before? and have you any ideas.
> > Our
> > IT department are stumped!!
> >
> > regards to all
> >
> > Malcolm
>
>
>

Nick

Did you receive my email with workbook attached? We have been having some
problems here at work with emails taking literally days to get through

regards

MalcUK

"MalcUK" wrote:

> Hi Nick
>
> Thanks for the reply, sorry for the delay in replying have been away from
> the office since last Wednesday. Most of the dept is on 2000 but as new
> machines are installed in the office they come with Windows XP operating
> system which seems to be having the problem with the spreadsheet. Will send
> you the workbook , please don't laugh at me attempts at VBA coding!!
>
> regards
>
> Malc
>
> "Nick Hodge" wrote:
>
> > Malcolm
> >
> > Are you upgrading to Windows XP or Office XP? There should be no
> > difference.
> >
> > I have Office 2003 installed, if you'd like to send me the workbook I'll
> > give it a test
> >
> > --
> > HTH
> > Nick Hodge
> > Microsoft MVP - Excel
> > Southampton, England
> > nick_hodgeTAKETHISOUT@zen.co.uk.ANDTHIS
> >
> >
> > "MalcUK" <MalcUK@discussions.microsoft.com> wrote in message
> > news:0B1760D3-55C3-4CD6-9293-A6A6D18E159A@microsoft.com...
> > >I have an Excel workbook composed in an Office 2000 system that works
> > > perfectly. It contains various bits of VBA and macro, nothing complicated,
> > > controling how user can insert lines etc., shutting the workbook if there
> > > is
> > > no input for 15 minutes(using ontime), hiding different bits of data
> > > depending on a control button.
> > >
> > > As I have said it works perfectly until; we are now upgrading to XP and it
> > > does not work at all with that operating system. Sometimes it will load
> > > and
> > > then hang when you try to exit and some times it hangs on loading
> > > resulting
> > > in the MS "Microsoft has encountered.......etc etc; do you want to send an
> > > error report?" screen.
> > >
> > > We have tried REM'ing out all the code in the Workbook Open module but we
> > > still have the same problem/ s Clearly there is somthing that the OS
> > > doesn't
> > > like. Has anyone encountered this problem before? and have you any ideas.
> > > Our
> > > IT department are stumped!!
> > >
> > > regards to all
> > >
> > > Malcolm
> >
> >
> >