S
Stephan Steiner
Hi
I was under the impression that in order to ensure that I'm only using non
empty columns I could use the IsXyzNull() method of the various Row types
defined in PSI. .
for instance, here I'm trying to add a bunch of enterprise resources to a
project plan - so I first check if the resource, identified by its NT
account, is already part of the project, and if not I look it up in the
enterprise pool using the Resource service. Then I create a new line for
ProjectDataSet.ProjectResources and copy all the fields from the
ResourceDataSet.ResourcesRow to the ProjectDataSet.ResourceRow (as long as
they exist in both rows) - in order not to run into any problems I'm using
the IsXyzNull() methods on the ResourcesRow - still, my first line already
fails.. when I'm calling ResourceDataSet.ResourcesRow.IsCREATED_DATENull() I
get an ArgumentException ('column' argument cannot be null. Parameter name:
columm) which seems to indicate that the ADO mapping is messed up - of
course I can go through the table rows the traditional way and check for
DBNull values, but isn't the point of having the PSILib to not having to do
that?
Regards
Stephan
I was under the impression that in order to ensure that I'm only using non
empty columns I could use the IsXyzNull() method of the various Row types
defined in PSI. .
for instance, here I'm trying to add a bunch of enterprise resources to a
project plan - so I first check if the resource, identified by its NT
account, is already part of the project, and if not I look it up in the
enterprise pool using the Resource service. Then I create a new line for
ProjectDataSet.ProjectResources and copy all the fields from the
ResourceDataSet.ResourcesRow to the ProjectDataSet.ResourceRow (as long as
they exist in both rows) - in order not to run into any problems I'm using
the IsXyzNull() methods on the ResourcesRow - still, my first line already
fails.. when I'm calling ResourceDataSet.ResourcesRow.IsCREATED_DATENull() I
get an ArgumentException ('column' argument cannot be null. Parameter name:
columm) which seems to indicate that the ADO mapping is messed up - of
course I can go through the table rows the traditional way and check for
DBNull values, but isn't the point of having the PSILib to not having to do
that?
Regards
Stephan