My company (The Catholic Diocese) has an access DB that they use to track happenings at the various parishes. This DB is tied to another access DB to insure that information such as parish names, priest names . . . can not be changed as users update the parish information. The forms that are used to update the DB are contained with in the access DB itself.
A request has come down that the database should be web enabled and use an InfoPath forms front end so that the parishes can themselves submit the DB updates directly to the DB rather than returning their entry data to a central person who must then enter the data for all 130 parishes.
In my research I've read about web services and am interested in generating a web service so that the InfoPath form can talk to the Access DB and submit/retreive data according to the InfoPath forms.
What I need to know is Since the DB I want to update is tied to a second DB, how will the web service interact with both DBs at the same time? can it even do that? the other thing to consider is that the second DB is setup with username and password access.
Since a modification from desktop to web based is required, why no use this opportunity to get away from ms access and migrate all data into MySQL that will still run in the same infrastructure you already have and that will be more user friendly for web base interfaces.
Once all the data is in MySQL you can use PHP you create the forms to input, update and view data. You can even use Drupal, a PHP framework to speed up the process while maintaining a high control in the security of the site.
The migration to MySQL and PHP will have another benefit and that is the reduction of cost for licenses of Microsoft products. There will no more need of MS Access on each computer to access the application as well as a change in your infrastucture from windows servers to Linux servers.