W
wjasonstrutz
My office is currently migrating servers, which is causing headaches in
migrating forms that use secondary data sources. I've run into the same
problems when switching from a testing database to a live form, essential
because you don't want to mess up live data when testing your Infopath form.
I'd like Infopath to have a shared data source feature. At present,
whenever I alter a form to use the live database, I have to change all the
data connections to point to the live database. Then I have to make sure to
copy the queries, because when I change the database for a data source, the
wizard asks me what tables I want to add. Then I might have issues with the
binding of fields, if I made a mistake in the previous step. If there's a
problem with the binding, then I have big problems with resetting the
conditional formatting and other features on various controls. It's a big
headache.
It would be much easier if there could be a shared data source, which spawns
different data connections that can be used in the schema. This way, I could
change the database that's used with one step, and if necessary, change the
data connections manually.
jason.
migrating forms that use secondary data sources. I've run into the same
problems when switching from a testing database to a live form, essential
because you don't want to mess up live data when testing your Infopath form.
I'd like Infopath to have a shared data source feature. At present,
whenever I alter a form to use the live database, I have to change all the
data connections to point to the live database. Then I have to make sure to
copy the queries, because when I change the database for a data source, the
wizard asks me what tables I want to add. Then I might have issues with the
binding of fields, if I made a mistake in the previous step. If there's a
problem with the binding, then I have big problems with resetting the
conditional formatting and other features on various controls. It's a big
headache.
It would be much easier if there could be a shared data source, which spawns
different data connections that can be used in the schema. This way, I could
change the database that's used with one step, and if necessary, change the
data connections manually.
jason.