K
KevinW.
I have an InfoPath 2007 browser enabled form that retrieves data from a sql
server database and submits the data back to the database via a web service
and also submits the form to a SharePoint Forms library. The problem is
trying to edit the form after the submit process when the form is opened in
the browser (Everything works fine when the form is opened in the InfoPath
Client). The submit process is as follows...
1. Submit the data to a web service which handles the inserts, updates, and
deletes. This part works.
2. Since the database uses Auto-numbering fields as PKs, i retrieve the PK
of the parent table so that the PK data is saved with the form. This part
works.
3. I then query the database just using the data connection (no code) so i
can get all the PKs for the child table records back into the form. This
part works.
4. I then submit the form to a sharepoint library. This part works.
What's happening is the optional fields that were left blank are disabled in
the form and can not be edited. I believe what is happening is those
optional fields are NULL in the database and when i retrieve that data back
into the form (in step 3 above) the datasource fields that receive those NULL
values no longer exist in the form which disables the controls associated to
them.
Is there any way to keep data source fields part of the form when an ado
connection returns NULLs?
Any suggestions will be appreciated.
Thanks,
Kevin
server database and submits the data back to the database via a web service
and also submits the form to a SharePoint Forms library. The problem is
trying to edit the form after the submit process when the form is opened in
the browser (Everything works fine when the form is opened in the InfoPath
Client). The submit process is as follows...
1. Submit the data to a web service which handles the inserts, updates, and
deletes. This part works.
2. Since the database uses Auto-numbering fields as PKs, i retrieve the PK
of the parent table so that the PK data is saved with the form. This part
works.
3. I then query the database just using the data connection (no code) so i
can get all the PKs for the child table records back into the form. This
part works.
4. I then submit the form to a sharepoint library. This part works.
What's happening is the optional fields that were left blank are disabled in
the form and can not be edited. I believe what is happening is those
optional fields are NULL in the database and when i retrieve that data back
into the form (in step 3 above) the datasource fields that receive those NULL
values no longer exist in the form which disables the controls associated to
them.
Is there any way to keep data source fields part of the form when an ado
connection returns NULLs?
Any suggestions will be appreciated.
Thanks,
Kevin