mibuso.com

primary key: basically its a unique identity for each record. Its the first key in the keys menue. It is used to differenciate between two records.

Thast all i remember.

Basically, this is what my manager told me and I need to write code to for this:
"If the Program Setup contains default Job Task No. then don't even add the job tasks from the job to be copied.
If the new job doesn't have a job task defined, only then do you copy the job task from the job to be copied
If the new job contains job tasks (done through Program Setup), then you skip copying job tasks"

Now I sorta, know where I am going.

This is sorta off topic, how do you delete a message in a post??? Is that even possible?

Well that makes absolutely no sense at all. Of course the new job is not going to have a job task. It's a new job, so it doesn't have anything attached to it when it is created. You must be working in a database that has customizations in there.

The reason why I am asking about primary key is because if you really understand that, you will also understand how filters on a compound primary key will affect what you need to take care of for a new job. The job task are related to the job by way of the job number, so when you copy a job task from one job to another, all you need to do in the new job task is use the new job number.

Filter on the old job number, loop, copy the record and change the job number, insert.

You are right, there have been a lot of customization's done for this client.
For Instance, when a user creates a job card, it will automatically fill it with a default information for job task (Thats why when a job a created it will have a default job task no., Cost Center Code, etc)

From the requirements my manager told me to do: I wrote this code and I thought it should have worked, but its not working. I have tried debugging it 5-6 times, but debugger keeps on crashing.



Any idea what might be causing the debugger to crash. I am pretty sure there is a flaw in my logic somewhere.

I'm sorry, I can't help you there. There can be a bunch of things, and to troubleshoot that you really need to have direct access to the screen. This is where you would sit down with your senior and step through the code together and troubleshoot what you see.

Ok.

Just one last question (I refuse to give you on this):
According to my manager this is what needs to be done. I have read these lines like atleast 50 times, I just want to run by you what I understood and you can tell me if I am on the right path.

1) "If the Program Setup contains default Job Task No. then don't even add the job tasks from the job to be copied. --> If ProgramSetup has a default Job Task No. assigned to it, then we should not copy any Job tasks

2) If the new job doesn't have a job task defined, only then do you copy the job task from the job to be copied --> This will never be the case, since when we create a job, it will always has a default job tasks, so I dont have to copy anything since it will never be empty (doesnt have job task). I am not really sure about this point.

3) If the new job contains job tasks (done through Program Setup), then you skip copying job tasks" --> This is basically the same thing as 1

If your manager gives you a requirement that you don't understand, you should not be asking ME to clarify. Go to the source and have them explain it, and explain it again, until you understand what they mean.

That actually makes senses...hehehe....