Sure! Tech support told me to install the latest patches for 5.0. I did,
with no change. Since I will have to start all over again with the
database copy and conversion, I haven't done anything else with it. I've
had a million other things to do, and 4.0 is running fine. Soon, I will
let tech support know that I still have the problem and will then work with
them toward a solution.
I searched through the group postings and found that someone else had this
exact same problem a while back. I didn't see anywhere that it had been
fixed, or at least that the solution was posted.
-Gary
From: "Troy Funte" <tfunte@...>
Gary,
It's a bit late now... but can you update us on your situation?
Troy Funte
Liberty Electronics
with no change. Since I will have to start all over again with the
database copy and conversion, I haven't done anything else with it. I've
had a million other things to do, and 4.0 is running fine. Soon, I will
let tech support know that I still have the problem and will then work with
them toward a solution.
I searched through the group postings and found that someone else had this
exact same problem a while back. I didn't see anywhere that it had been
fixed, or at least that the solution was posted.
-Gary
From: "Troy Funte" <tfunte@...>
Gary,
It's a bit late now... but can you update us on your situation?
Troy Funte
Liberty Electronics
----- Original Message -----
From: ggrenier@...
Subject: [Vantage] NO-LOCK status!
Upgrade from 4.0 to 5.0 went fairly smoothly. I got the data collection
terminals up and running, only to be told that they're getting the
following message when they try to enter a job:
"JobOper record has NO-LOCK status, update to field not allowed. (396)"
They click OK and get the next message:
"Unable to update JobOper field. (142)"
Has anyone seen this?
Gary Grenier
IT Manager