deburr
|
Lynn, I have not done a lot of testing but it seems isolated to the one workstation. Would a memory or other hardware problem cause this? The person that is having the problem, does 98% of the data entry on this workstation, so it is logical that the rest of us just don't have enough exposure to run into this on other workstations. I do have occasional problems with another database program that locks up on some print jobs. This is why I am leaning towards hardware issues. The errors relate to reading memory locations. Thanks, Steve
|