Thanks for the reply. I was hoping and looking forward to see if you would help me with my coding (even dreamt a little on this), but then I see more of old sayings "give fish or teach how to fish". All I want to do it GET THIS DONE and BE DONE WITH IT. And if there's problems later, it is either I am still working here or it's someone else's problem.

Yes, I am familiar with the below:

LOCAL lcOldDeleted
lcOldDeleted = SET DELETED()
SET DELETED OFF
*!* Do stuff here with deleted records
SET DELETED &lcOldDeleted

But, like I said before, I spend a whole year on this project and was about 2 weeks before it's all complete to go out for use. Then, this boy walks in with some face and says "Gotta do it over again." So, my give back is he have to tell me how he wants it (which he does not know what he's really talking about). I even argued with him that there is a need for the 'Revert' button, but he says no... without a guess, he wanted it back but call it 'Esc' (to make it look like he's knowing what he's doing). On top of that, I asked (here) about how to do a button for adding JPEG image (signatures) and came up with three nice buttons (Add/Edit, Delete, Exit), and the moment he saw it for the very first time, he came back and said, "Take it all out." Huh? He even asked me about how would others be able to do that and would like something to be done about that, so I did, now this? Sorry to cry baby here.

Since this code works, I am going to leave it like this, It WORKS, right? If you can show me where I can be wrong with this code (that I copy/paste in the post before this), weather it's INDEXSEEK or whatever, I would appreciate you correct me and I will change it. Like I said, I want to be done with it. I got too much garbage from here (work), there go another saying...GIGO, you know. I wanted to go forward with the power VFP but "they" are holding me back with "DOS" thinking.

Yes, I am looking for another position, but I have to be careful how fast I move, I aren't got money backed up, like lot of people with grands in the bank (admittedly, as of today, I got $25 in my account and got nothing else invested).

Chuck

>It's difficult to say exactly, but there are always problems when one moves from FPW to VFP and continues to code in FPW. It sounds like your supervisor is steering you toward bad habits by still using memory variables rather than insisting that you learn to do things a new way. Due to the politics where you are, if I were you I would save email or whatever that shows the supervisor telling you to do it this way. Most job descriptions specify that you code according to in-house standards and if anyone questions your coding style you can pull out the email and say that you were coding according to standards.
>
>At the same time, I would seriously look for another opportunity. I know your current job pays well, but living in Hell because it pays the bills is not a good idea in the long term. Look for an opportunity to become the best software developer that you can be, especially if you can work with some other people who really know what they're doing.