Orginally posted by Kevin Hall
First suggestion: profile your code. See if there are any easy to identify bottlenecks
Ok.

Orginally posted by Kevin Hall
Second suggestion: Give us something to work with. If you can't share code, can you share the psuedo code? Flow chart? We can only guess what might be wrong if you can't share what's happening.
Hummmmm...


Orginally posted by Kevin Hall
Third suggestion: Tell us what your program does. What exactly are you trying to process? Where is the data coming from? Where are you writing the output to? How much data are you analyzing? What do you have to do to the text?
Please Kindly read my previous replies.Thank you.


Orginally posted by Kevin Hall
Fourth suggestion: Check for common string manipulation performance killers:

* unnecessary copying of string data. See if you can return references to strings instead

* inserting / removal of text in the midlle of a very large string. If this operation occurs often, it's usually quicker to read data as a vector of smaller strings -- for example a text file can often be read as a vector of text lines.
Yes, you are right, I will look at it.

Orginally posted by Kevin Hall
Fifth suggestion: Hire a contractor. If you don't want to debug it yourself, there are a lot of people out there willing to do it if they get paid.
Hahaha, hey friend, actually it is written by some other programmer, otherwise I would have tried to find the problem.

I can debug, I believe it takes long time.
for example, this application calls a funtions for checking spaces in the input file for more than 1 million (100000) times!!!
And lots of while and for loops are there.

Now I'm trying here for any luck (I mean any help from you gurus...)
If no luck then I have to sit and debug...
That's really very scaring me......

Thanks...