E
Emily
We are using MS Project 2002 Server and all the clients are using MS Project
Professional.
Oee of our PMs was working on a plan for a number of months without any
problems. They had not yet saved their baseline. Then one day they opened
the plan and received an odd error message:
An import error occured
Check row 620 column ASSN_BASE_WORK
This is not a valid work value or is outside the range for this column.
For Work resources, type the work amount and the abbreviation for the time
period, for example "12d" or "4hrs".
For Material resources, type the work amount alone plus the Material label
you created for the resource, for example "8 tons"
To continue importing with additional error messages, click Yes
To continue importing with no error messages, click No
To stop importing, click Cancel
My PM, at this time, deleted the offending row, saved the file and then
reopened it. The error message reappeared, now identifying the next row in
the plan.
I tried deleting the file then re-importing it from an archive but the error
message came back again.
I took a look in the offending DB, but found nothing out of the ordinary,
especially since it seems to be a Baseline dB and this plan did not have any
baseline saved.
I have also looked on Technet but to no avail.
The user can continue to work with the software, and the plan does not seem
affected by the message, the baseline, now saved, is all right. It does,
however, create a minor inconvenience to the user.
thanks,
Emily
Professional.
Oee of our PMs was working on a plan for a number of months without any
problems. They had not yet saved their baseline. Then one day they opened
the plan and received an odd error message:
An import error occured
Check row 620 column ASSN_BASE_WORK
This is not a valid work value or is outside the range for this column.
For Work resources, type the work amount and the abbreviation for the time
period, for example "12d" or "4hrs".
For Material resources, type the work amount alone plus the Material label
you created for the resource, for example "8 tons"
To continue importing with additional error messages, click Yes
To continue importing with no error messages, click No
To stop importing, click Cancel
My PM, at this time, deleted the offending row, saved the file and then
reopened it. The error message reappeared, now identifying the next row in
the plan.
I tried deleting the file then re-importing it from an archive but the error
message came back again.
I took a look in the offending DB, but found nothing out of the ordinary,
especially since it seems to be a Baseline dB and this plan did not have any
baseline saved.
I have also looked on Technet but to no avail.
The user can continue to work with the software, and the plan does not seem
affected by the message, the baseline, now saved, is all right. It does,
however, create a minor inconvenience to the user.
thanks,
Emily