Well - it seems I am justified in holding back on turning on EVO Notes. (other than the moaning I hear from other posts)  Right now they are turned off, but I am frequently getting spurious notes tacked onto the end of Purchase orders.  I just printed one that had a note tacked onto the end that was associated with a different vendor.  Went into the vendor for that PO and sure enough, there is a CSN note in there that looks like it was copied from the other vendor - the problem is, it won't let me delete the note!  It acts like it does, but it remains.  The only thing I can think of trying is changing it to a CSH note and hope that it won't show up the next time I create a PO for this vendor.  Right now, our Purchasing person has to review every PO she creates, and delete spurious lines, which decreases her efficiency considerably.

I think the reason that you are not getting any answers is that it is very hard to come up with an answer when 99% of users are having no problems and tech support cannot repeat the error on test systems.
 
I know IS Tech is working on this, but I'm sure they need more info. If someone can help to pinpoint when and under what conditions this is found it would definitely help. We use both old style and Evo notes here for our customer accounts (some users have old AR-A programs, some use the T7 version), but I have not seen it nor can I seem to cause it to happen.  
 
Also, note that you don't "turn on" Evo notes, they are part of the T7 programs by default. Turning Evo notes on or off makes them print or not print. So please give as much detail as possible about what you are trying to do, which type of notes you are using, which RTMs are printing.
 
This may be one of those things that takes awhile to find, but it will probably be an easy fix once it is isolated.

It really sounds like one of the notes files has a problem, either the one that has the pointer to the actual notes, or the one that holds the notes. Sounds like the two files are not communicating properly. It would make sense that you could not delete the errant note if the problem was the pointer. Very interesting. I hope this gives Allen a bit more to go on.

I guess I should not have implied the vendor entries happened sequentially - they didn't - it was more to show that the notes from one vendor showed up in another.  I was only able to find the mystery note source because they were specific enough to figure out who the vendor was.  We have others that pop up where we can't figure out which vendor this not is from - not that it matters, since you can't delete it.  I wonder if I delete it in the vendor it belongs to, if it will disappear from the wrong vendor........

What the heck - I tried a test PO and VIOLA - the note is not printing.  SOOOO - for the time being, when a spurious note shows up, I will tell purchasing to go in and change the note type to HID and it will stop.

AH - well, lets check....and the answer is.....(holding envelope against forehead)....no it does not.  The good note on the correct vendor stayed as a CSN - the spurious note on the other vendor is now an HID - don't know how this affects the theory of a bad pointer, but there it is.

This information does help.  Just wish it was definitive enough to identify the exact problem.  Has anybody had customer notes show up on a vendor or vice versa or do they stay in the same area as far as that is concerned?

I was pointed here from a recent post I started yesterday.  One thing I noticed is that the notes that have "jumped" venders all seem to be near each other in the alpahbet.  Out of the six messages that jumped - I had A's, A's & B's, B's, B's & C's, and J's.  On most of them, there is one good vender-note match and the match is with the last vender of the group showing the note.  Don't know if this helps.  I found which ones had notes by looking in maintain database under bkapvend.b under the notes and I made a list of all the vender notes and had purchasing tell me which ones were good.
 
Darla Long