|
It means pretty much
what it says -- the database couldn't update because it is locked by something
else, namely the poster.
If you hit this
error, open up the poster dialog right away and make sure that there aren't any
errors in the log. That is about the only thing that can go seriously
wrong here. Otherwise the error is basically just an
annoyance.
I have not see this
error many times even with pretty big databases, so if she is getting this "a
lot" (whatever that means), please let us know. Maybe there is something
deeper happening here that I am missing.
This might also be a
little better with very recent 1.17s, but I wouldn't upgrade her to 1.17 just
for that reason. You might try the 1.11.12.2 release however, which fixes
a performance problem with the poster (not that there is a bugtrack or
swannounce for it). The locking problems start when the poster gets
backlogged. I would really like to spend a few months on database
locking issues (including supporting SQL server for big accounts), but that will
mean allocating a few months to do it. That's hard to do when you can't
show sales/mgmt any new "features" after the few months have
passed.
Ken
|