first, NOBODY HURT ME PLEASE   
didn't mean to start a war hehehe

I bypassed the overwrite in the file itself, but I can't bypass it when you go to retrieve specs... I personally can live with it but nobody knows the whiney voice I must deal with on a daily basis when the data entryperson can not remember that end-shift or deleting all the characters is required...    think of a dentist's drill being ran across a chalkboard and you are almost there *insert chill in spine here*

I created an add/remove field so all she needs to overwrite is the part number she is looking for and that has already proven itself extremely useful.  Now all I need to do is figure out a way to clear the entire form when she hits F7...

Its been kind of funny having her search for a number I know is in there, but when she forgets to delete the previous search criteria she says its not in the computer and tries to add it again as a new number.  OH well I will get through this 

Kerinst, we have a similiar situation in our pricebook. We have to udate our material prices each month from our suppliers.
To avoid getting incorrect prices by not deleteing or overwriting the existing prices I did the following.

LE of purchase price and updated
I added 4 additional LE's (read only) named prev date1, prev date2, prev  price1 and prev price2.

on entry of Purchase price

If @Update
then
Prev Price1 = Purchase Price
Prev Date1 = Updated
Prev Date2 = Prev Date1
Prev Price2 = Prev Price1
Clear(Purchase Price, Updated)

Quick and simple, clears the LE and gives a past history of pricing.
hope it helps