G
Gregs List Acct
In my scenario I have about 5 secondary datasources that I clone into on
offline xml node. When the form is off-line users can add/remove/update
items in those cloned nodes.
When the user goes back on line I'm using custom code to call SQL Stored
procs to make those updates back to SQL since Infopath's submit only handles
the Main datasource. As a result, I have to create an ADODB.Connection and
ADODB.Command, and the users get a security warning about ActiveX objects. I
can trap the error if they tell IE not to allow it, but I was wondering if
there was a way to leverage the existing secondary datasources'
dataconnections so they only deal once with telling IE to allow the code to
run.
Does that make sense?
offline xml node. When the form is off-line users can add/remove/update
items in those cloned nodes.
When the user goes back on line I'm using custom code to call SQL Stored
procs to make those updates back to SQL since Infopath's submit only handles
the Main datasource. As a result, I have to create an ADODB.Connection and
ADODB.Command, and the users get a security warning about ActiveX objects. I
can trap the error if they tell IE not to allow it, but I was wondering if
there was a way to leverage the existing secondary datasources'
dataconnections so they only deal once with telling IE to allow the code to
run.
Does that make sense?