Sergei
Thanks! That was clue enough for me to find the problem. Final solution was to create a Variant variable, copy the field value into the new variable, and use the Variant as the parameter for EditCellValue. It was insufficient to cast the field value (using CVar); had to use an explicit Variant variable.
Some other points I learned along the way:
The field in the recordset is a LongInteger and the field in the shapefile is FIELD_INTEGER. I thought they would be compatible. Tried casting my variable into Integer, but its value is too large for Integer so that was not a solution in this case.
I thought I may have made a mistake in the Precision and Width definitions in the EditAddField statement, so I reversed their order. With the values in the "wrong" order, the code still generates a valid FieldIndex number and the LastErrorCode value is zero. However, the resulting DBF does not contain the field (as it should with a faulty field definition). Seems like a bug - it should raise an error code if the field can't be created.
The EditCellValue statement did not raise an error (LastErrorCode = 0), and it returns a TRUE value, even when it fails to write the value into the table. However, when I single-stepped through the statement, it jumped into the callback error function, which is where I actually saw the incompatibility with the variable types. I think it should return an error code if it fails to write into the table.
StopEditingShapes returns a False value, but with a LastErrorCode=0 when used on an in-memory shapefile. Probably debatable, but I think returning a True value would be more appropriate in this situation.
Making slow and steady progress on getting my program operational! Thanks again for the help.
Jack
Thanks! That was clue enough for me to find the problem. Final solution was to create a Variant variable, copy the field value into the new variable, and use the Variant as the parameter for EditCellValue. It was insufficient to cast the field value (using CVar); had to use an explicit Variant variable.
Some other points I learned along the way:
The field in the recordset is a LongInteger and the field in the shapefile is FIELD_INTEGER. I thought they would be compatible. Tried casting my variable into Integer, but its value is too large for Integer so that was not a solution in this case.
I thought I may have made a mistake in the Precision and Width definitions in the EditAddField statement, so I reversed their order. With the values in the "wrong" order, the code still generates a valid FieldIndex number and the LastErrorCode value is zero. However, the resulting DBF does not contain the field (as it should with a faulty field definition). Seems like a bug - it should raise an error code if the field can't be created.
The EditCellValue statement did not raise an error (LastErrorCode = 0), and it returns a TRUE value, even when it fails to write the value into the table. However, when I single-stepped through the statement, it jumped into the callback error function, which is where I actually saw the incompatibility with the variable types. I think it should return an error code if it fails to write into the table.
StopEditingShapes returns a False value, but with a LastErrorCode=0 when used on an in-memory shapefile. Probably debatable, but I think returning a True value would be more appropriate in this situation.
Making slow and steady progress on getting my program operational! Thanks again for the help.
Jack