I've not worked with the PIC14000 chips yet, however two thoughts:

1) I suspect that you don't need accurate calibration info loaded for a
ALL proportion of your development time? (unless trying to sync serial)

2)if you set up the calibration data info as data to be assembled into 
the hex file then you can use the if def statement series in MPASM to
automate the equivalent of your copy/paste labour and you can def the
S/No of each JW part prior to assembly/burn in.

3) Use the CBLOCK directive (again if using MPASM) to define each 14000
JW parts cal mem values, starting at an ORG of  h'0FC0'. These file/s
can be "include"s to reduce your main file size.

regards,
Graham Daniel

Morgan Olsson wrote:
> 
> I am developing a program in a windowed PIC14000.  It is factory
> preprogrammed with calibration data for oscillator, wdt, bandgap etc.
> 
> Problem: First time I erase it I will loose the calibration data in the chip.
> 
> I trying MPLAB 3.40.
> For now, I read the target, then use Window\Calibration Data... , and then
> copy-paste each value to a special file within project, keeping all chips
> all calibrating data.
> 
> And when programming, the same way reverse.  Easy to make errors.
> 
> There should be, and probably is, a way to save calibration data to a file
> for each of my developement chips, so I can import them when programming.
> 
> I use 6 numbered chips, cycling them between programmer, prototype and eraser.
> Don«t tell me about emulator; there is nor space, power or money enough  ;)
> 
> Regards
> /Morgan
> 
> /  Morgan Olsson, MORGANS REGLERTEKNIK, SE-277 35 KIVIK, Sweden \
> \  mrt@iname.com, ph: +46 (0)414 70741; fax +46 (0)414 70331    /