Hi! I'm having a problem when entering sales orders... I'll get the header filled out, but when I try to move on to the line item screen, I get an error message "BKSLMSTR in use by another user". (I'm paraphrasing) I have noticed that this seems to happen when my boss is paying bills (accounting-ap-b) in the evo system, and clears when he is out of it.  
 
Is this supposed to happen? If so, is there a way around it so that he can work and I can still get the sales orders done in a timely manner?

I suspect you're right about me getting the error message wrong... I was doing it from memory, without it in front of me.  
 
The problem isn't a one time in a thousand type of thing, if that helps...  I am consistantly locked out of sales for the entire time his computer has AP-B open.

I'm on Evo-erp version 2006.1 8, acording to the "about" page. I'm not above thinking that it could be unique to my system or something, but I do need to know how to solve the problem...
 
Did you do your test on the same machine, or did you have ap-b and so-a open on different machines (which is what is happening to us)?

Just tried the same thing(s) running AP-B on one machine and SO-A on another. Sorry, but no problems here.

further explaination of original problem - on the system being used by captkahuna
 
I used the monitor to watch the lock status of bksymstr during the manual check writing procedure.
 
a 'single' lock appears upon hitting return on the '...want to reset check number counter' question and remains until the 'did the check print properly' question is answered.
 
what is happening is that the person writing the check agrees with the suggested next check number, saying yes to reset counter, yes to print manual check, selecting graphical form, then previews the check, then prints.  The whole time bksymstr is locked until then 'printed propery' question is answered.
 
the person writing checks is new to evo and still checking all keystrokes carefully. I'm not sure there is a better way to handle the lock for check number in that until the check prints properly you probably don't want to update the counter but you also don't want someone else to get your check number while your trying to print a check.  
 

I think the only thing that can be done is to get the person writing checks comfortable enough with the process that they just print them and say they printed ok. Unless you can get ISTS to rewrite the way DBA works, which I suspect would be extremely extensive.