-
They must be opened seperately and printed individually.
-
Add another control, like a repeating table to display the data set that is in the list box.
-
Any data you want in the database must be put in the DB.
You may need a sub table relationship for the additional repeating section.
Other fields added to the form do not go to the DB unless they are existing fields.
-
You have to fool it a bit and use a submit type connection.
I think Greg has a blog post on this.
-
Either a web service or use integration services to mirror data from Oracle to SQL and then connect to SQL.
-
Unfortunately calculated fields are not available in data connections.
Typically you have to combine the data within the form.
-
Large dbs are an issue.
Ideally you can use a web service instead that can query the records instead of loading them all.
You can maybe reduce the number of fields that are being loaded.
-
Sql is straightforward and there are examples here and on Microsoft's site. Oracle is not possible without web services.
Start with a database and crete a new form or check out qdabra's web service package.
-
Sharepoint has an issue with Access.
One thing also is to make sure that the location is writable for the users who need to use it.
Typically you create another file share that is accessible to everyone you need.
-
You need to know the URL to the web service but then it is just running through the data connection wizard.