stop...please...just stop!

School A and School B live in one database. This makes life interesting for me, but it's also ensuring TONS of job security. So I guess I shouldn't complain, but I'm good at it. So here goes.

A student is currently enrolled at School A. Plans to withdraw and attend School B. I get a request...

"Please change the students campus from School A to School B so I can enroll the student."

Me: "I can't do that. First the system is designed to prevent us from changing the campus of a currently enrolled student. Second, School B is an entirely different school from School A. We have decided to proceed as if they were in a seperate database. This means we will need to keep two files for the student for our reporting purposes, within the database. I see there is already a duplicate record for School B in the database. You should log the enrollment in that record."

Two hours later. A second request from the SAME PERSON!

"Please merge the two records for this student together.These are duplicates"

Me: *annurysm - head explosion - grey matter on my screen - spurt spurt - darkness*

How do I respond to this?

I feel I explained two hours ago there will be two records. I condoned her having two records, I explained why we need to have two records...and still...she wants them merged together....no.

At this point I am left wondering...
A. Did you not read my first message?
B. You must have read my first message, you did get the part about enrolling him in the 2nd record
C. Did I not explain well enough?
D. Is this an elaborate game that harkens back to childhood in that, 'if mom says no - i'll ask dad'.

Well guess what? I'm mom and dad, and I see all! And I still say NO!

Now I have to go eat my salad because if reply to the new request now I'll reply with; "Yes. There are duplicates. *head pat* Duplicates good. Two School make Two File! Live in Peace! Peace! Yes - duplicates! Duplicate wanted now. *cookie*