Give some of the code where you might think is giving delay. Sometimes you
think it works well but actually, you may have used long drawn coding that
uses too much referencing. Old win98 was great because it used very little
graphics and ram. but WinXP uses a lot more ram and your sub routine maybe
extensive. Maybe if you break up the routine into several routines. Also if
a variable is no longer used in one part of the macro then "release" it as it
is still taking up memory.
eg: Dim intNum as integer
Dim strMsg as String
intNum=100
strMsg="If you have encoutered this message then an error has occurred."
(code)
intNum=0
strMsg=""
(more code)
"Prince" wrote:

Hi All,

I have a strange issue.

The application coded in excel 2000 is not performing nicely in excel
2003.

I have gone through the folowing link:

http://www.mvps.org/dmcritchie/excel....htm#excel2003

The steps like switching to calculation manual and then screen
updating= false is taken care in my code.

The functions like offset() and other volatile functions which are
used is same for excel 2000 and excel 2003, then I fail to understand
why it is taking more time.

Even some of the links asked to install the drivers. I have
application which I have coded in 2003 which are performing better but
they are not taking care of much of reporting.

I have gone throughn the following links:
http://www.decisionmodels.com/calcsecretsc.htm

http://groups.google.com/group/micro...ee7cd241b0a295

http://groups.google.co.uk/group/mic...+to+excel+2000

http://help.lockergnome.com/office/P...ict570863.html

Please can some one judge the solution that what might be the problem
in calculations of the same functions.

I do understand it is a big application but what might or what
settings might have changed that the same functions are taking double
time.

Please reply out of the box as I am in need of all my friends advice
and expertise.

Thanking all of you,

Regards,

Prince