Merging tables autofills fields. How to avoid this?

Discussion created by normaste on Oct 6, 2010

I'm merging two tables containing different fields using the IBasicGeoprocessor method in vb. The merge goes through okay, leaving the fields not required for the first set of items blank. For the second set of items, fields that should be blank are filled in with information from the last item of the previous set of items. I'm wondering if there's anyway to ensure that fields stay blank if the incoming data doesn't have that field.

Thanks in advance,