Haha...I think ive seen it all when it comes to screwing up labor collection, fun stuff.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Mike Abell
Sent: Tuesday, October 29, 2013 12:56 PM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Scheduling dates in ResourceTimeUsed error - Vantage 8.03
Thanks guys, I think the problem started because someone "completed" the operation manually while this person was STILL clocked into it and that screwed everything up. At least that's what I "think" happened.....
Mike Abell
Information Technology Manager
Flexial - BOA Group - Cookeville, Tennessee
Office: 931.432.1853 ext 302
Mobile: 615.418.3055
email: MAbell@...
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Miguel Santillan
Sent: Tuesday, October 29, 2013 12:39 PM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Scheduling dates in ResourceTimeUsed error - Vantage 8.03
You should also be able to go to the job operation, change it to anything else, save it, then change it back. Essentially you are removing the resource, writing the new resource to the table, then writing the old resource back to the table.
Miguel A. Santillan
Compass Manufacturing Systems
510-661-6666 Office
From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Rob Bucek
Sent: Tuesday, October 29, 2013 10:00 AM
To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
Subject: [Vantage] RE: Scheduling dates in ResourceTimeUsed error - Vantage 8.03
Did you try removing the job from the schedule, and then rescheduling the job?
From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Mike Abell
Sent: Tuesday, October 29, 2013 10:24 AM
To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
Subject: [Vantage] Scheduling dates in ResourceTimeUsed error - Vantage 8.03
We are getting the following error when an MES user is attempting to clock out of a job.....Anyone know what causes this or a fix.......
Message: Internal error. Scheduling dates in ResourceTimeUsed file are not consistent for : Job 24355-F35 Assembly 0 Sequence 10
Type: Error
Program: db/trg/joboper/WRITE.P
Method: RemoveLoad
Table:
Row:
Field:
Message: Internal error. Scheduling dates in ResourceTimeUsed file are not consistent for : Job 24355-F35 Assembly 0 Sequence 10
Type: Error
Program: db/trg/joboper/WRITE.P
Method: RemoveLoad
Table:
Row:
Field:
Message: Internal error. Scheduling dates in ResourceTimeUsed file are not consistent for : Job 24355-F35 Assembly 0 Sequence 10
Type: Error
Program: db/trg/joboper/WRITE.P
Method: RemoveLoad
Table:
Row:
Field:
Message: Internal error. Scheduling dates in ResourceTimeUsed file are not consistent for : Job 24355-F35 Assembly 0 Sequence 10
Type: Error
Program: db/trg/joboper/WRITE.P
Method: RemoveLoad
Table:
Row:
Field:
Mike Abell
Information Technology Manager
Flexial - BOA Group - Cookeville, Tennessee
Office: 931.432.1853 ext 302
Mobile: 615.418.3055
email: MAbell@...<mailto:MAbell@...>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Mike Abell
Sent: Tuesday, October 29, 2013 12:56 PM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Scheduling dates in ResourceTimeUsed error - Vantage 8.03
Thanks guys, I think the problem started because someone "completed" the operation manually while this person was STILL clocked into it and that screwed everything up. At least that's what I "think" happened.....
Mike Abell
Information Technology Manager
Flexial - BOA Group - Cookeville, Tennessee
Office: 931.432.1853 ext 302
Mobile: 615.418.3055
email: MAbell@...
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Miguel Santillan
Sent: Tuesday, October 29, 2013 12:39 PM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Scheduling dates in ResourceTimeUsed error - Vantage 8.03
You should also be able to go to the job operation, change it to anything else, save it, then change it back. Essentially you are removing the resource, writing the new resource to the table, then writing the old resource back to the table.
Miguel A. Santillan
Compass Manufacturing Systems
510-661-6666 Office
From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Rob Bucek
Sent: Tuesday, October 29, 2013 10:00 AM
To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
Subject: [Vantage] RE: Scheduling dates in ResourceTimeUsed error - Vantage 8.03
Did you try removing the job from the schedule, and then rescheduling the job?
From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Mike Abell
Sent: Tuesday, October 29, 2013 10:24 AM
To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
Subject: [Vantage] Scheduling dates in ResourceTimeUsed error - Vantage 8.03
We are getting the following error when an MES user is attempting to clock out of a job.....Anyone know what causes this or a fix.......
Message: Internal error. Scheduling dates in ResourceTimeUsed file are not consistent for : Job 24355-F35 Assembly 0 Sequence 10
Type: Error
Program: db/trg/joboper/WRITE.P
Method: RemoveLoad
Table:
Row:
Field:
Message: Internal error. Scheduling dates in ResourceTimeUsed file are not consistent for : Job 24355-F35 Assembly 0 Sequence 10
Type: Error
Program: db/trg/joboper/WRITE.P
Method: RemoveLoad
Table:
Row:
Field:
Message: Internal error. Scheduling dates in ResourceTimeUsed file are not consistent for : Job 24355-F35 Assembly 0 Sequence 10
Type: Error
Program: db/trg/joboper/WRITE.P
Method: RemoveLoad
Table:
Row:
Field:
Message: Internal error. Scheduling dates in ResourceTimeUsed file are not consistent for : Job 24355-F35 Assembly 0 Sequence 10
Type: Error
Program: db/trg/joboper/WRITE.P
Method: RemoveLoad
Table:
Row:
Field:
Mike Abell
Information Technology Manager
Flexial - BOA Group - Cookeville, Tennessee
Office: 931.432.1853 ext 302
Mobile: 615.418.3055
email: MAbell@...<mailto:MAbell@...>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]