Secondary Table Fields Are Un-Editable When Empty?

EArgen — Mon, 19 May 2014 14:16:02 GMT

Hi Everyone,

So I have two tables in SQL that I am trying to test out on InfoPath 2013 before I start building more of the database.

Table A

EMP_ID, FirstName, MiddleName, LastName

Table B

Address_EMP_IDFK, Address, City, State_IDFK, ZIP

Address_EMP_IDFK (Named poorly at the moment but I know what it's referencing) is a foreign key to EMP_ID, which is the Primary Key of Table A. This is so I can link employees by their number to various things, such as their address. State_IDFK is a foreign key to a lookup list of states and abbreviations.

My issue is this. When I have a repeating table, or even just a single field for each field, I am unable to select information in fields that do not have data in them.

For example:

EMP_ID FirstName LastName Address City State Zip

A A A A A A A

B B B B B B B

C C C C(Empty) C(Empty) C(Empty) C(Empty)

D D D D D D D

In this example employee C did not have his address information filled out. This leaves those fields empty. When I use a repeating list it will show exactly like this, which is what I want it to look like. The problem is that those empty fields are unable to be edited. They are not actually greyed out, they are simply empty and I cannot enter information. Note I am not talking about submitting data, just about physically placing data into the field whether it submits correctly or not. I can do this with every other field as long as there is information within those fields to start.

This is probably, and hopefully, a very newbie mistake either with the SQL tables the way they are set up or with how I am interacting with InfoPath.

Thank you for your help!

Edit: Please note I am not yet using a Web Service, so I'm only just querying the SQL Server to see if the concepts work. I wouldn't expect that to change anything, but I just thought I'd mention it!

Newbie Questions

Secondary Table Fields Are Un-Editable When Empty?