Primary Key and blank fields

[mbarsenas]

I have a database with a table that has 4 primary keys in one table. I
am usind RDA to push and pull. Before I went to RDA I was using merge
replication with no problem. The problem I am having with the push is
that when one of the primary keys is pushed it is blank so it is
considered a null and as we know...nulls are not allowed with primary
keys so as the upload continues, once it hits that key it returns an
error and that error is due to the blank left in the table. My question
is, How can I allow a primary key to allow blanks in the field? Not
nulls but blanks.

 

[John Vinson]

My question
is, How can I allow a primary key to allow blanks in the field? Not
nulls but blanks.

It's risky, because Null and a Zero Length String look the same... but
you can set the field's Allow Zero Length String property to True,
Required to Yes, and DefaultValue to "".

John W. Vinson[MVP]

 

[mbarsenas]

It's risky, because Null and a Zero Length String look the same... but
you can set the field's Allow Zero Length String property to True,
Required to Yes, and DefaultValue to "".

John W. Vinson[MVP]

Thank you very much. This sounds like the solution. I am having trouble
finding that option. I searched in the design table and properties of
the table, but I can't seem to find where to change that. Am I looking
in the wrong place?

 

[Douglas J. Steele]

Thank you very much. This sounds like the solution. I am having trouble
finding that option. I searched in the design table and properties of
the table, but I can't seem to find where to change that. Am I looking
in the wrong place?

With the table open in Design view, select the field in question, and look
at the bottom of the window. The three properties John lists should be on
the General tab.