Indexes effecting the save and edit times does make sense. As far the Application its self is concerned we have made all possible efforts to speed up the process of save and edit (I mean memory leaks, object destruction and creation and instantiation at proper times etc), that is why I was now concentrating on ways to make it better through indexes or any other means possible.

While what you said makes sense but following what others have helped me with also made considerable effect on the speed.

Which I think must be because:

"Before it actually saves the record it has to go through thousands of records to find the appropriate ID and its classtype (which we determine through a ClassTypeID) and then make sure that its using the correct ID Sequence to save the record. The lookup took a long time, which was saved due to correct indexes ( I Think )".

Any comments..?

Thanks.