InfoPath Dev

I have been designing my form so that it connects to an Access database

However, we have decided we no longer want the form to connect to Access, and it will instead be uploaded to a Sharepoint library for people to fill out (the info we were going to use in Access will instead be held in columns in Sharepoint)

 Is there anyway to convert my form from being bound to Access to being instead bound to itself?  Or is the best bet to just start over?

alexj:

However, we have decided we no longer want the form to connect to Access

based on what?
I was always thinking that decisions are made on the basis of accepting working alternatives not rejecting them without having elaborated and verified alternatives
It is better to have bad working solution than marvelous unverified ideas, plans and projects.

alexj:

and it will instead be uploaded to a Sharepoint library for people to fill out (the info we were going to use in Access will instead be held in columns in Sharepoint)

uploaded or published? form or form template?
Have you been using the same form for all users?

alexj:

Or is the best bet to just start over?

Who will bear the responsibility for this advice? 

My Self The Enemy:

based on what?
I was always thinking that decisions are made on the basis of accepting working alternatives not rejecting them without having elaborated and verified alternatives
It is better to have bad working solution than marvelous unverified ideas, plans and projects.

Based on learning that Sharepoint has an export function whereby columns can be exported into an Excel spreadsheet, and since this function exists it is not needed for the form to connect to Access, also, some features were having a difficult time with connecting to Access such as attaching files

My Self The Enemy:

uploaded or published? form or form template?
Have you been using the same form for all users?

 I don't know how to answer the first question yet . . . if I understand correctly it will go into a Sharepoint library.   It is a form template, but I believe when users fill it it becomes a form.   Currently users are using a paper form that circulates through interoffice mail through multiple buildings at several seperate locations to collect signatures, an electronic form is thus eagerly desired

My Self The Enemy:

Who will bear the responsibility for this advice? 

I will, though I don't think either choice will have much of an effect on my standing, just if I make the wrong choice will result in more tedious and annoying hours of Infopath use than if I make the right one . . . . also one of my goals is to absorb knowledge about Infopath, so I want to know what is the 'correct' way to go at times rather than just blindly charging ahead

Hi:

There isn't an easy way to convert the form, to the best of my knowledge - usually starting over is less trouble and isn't as laborious as I often expect it will be.

One thing to keep in mind is the way your library will expose any repeating data in your form - if you are promoting a repeating field, you have options for how to promote it, but if you have repeating data and think that SharePoint views may not be up to the reporting your end users have in mind, you may want to quickly prototype that portion, make sure they like the results in the library before you re-create the form entirely.

There will be a repeating field that will be used to attach files to the form (such as brochures, scans of receipts, grade card scans etc) but will not be used for generating reports

 I am making an Infopath version of this form (plus a few fields that have been discovered help) http://www.opm.gov/forms/pdf_fill/SF182.pdf

Idea - 

Users fill the form and also upload documents such as brochures to explain training

Sharepoint workflow sends form to collect signatures

Users later upload gradecards or similar to show successful completion of training

Exported from Sharepoint to Excel to generate reports

Hilary Stoupa:

Hi:
There isn't an easy way to convert the form, to the best of my knowledge - usually starting over is less trouble and isn't as laborious as I often expect it will be.

Hilary Stoupa:

<p>Hi:</p>you may want to quickly prototype that portion, make sure they like the results in the library before you re-create the form entirely

Also wanted to write: you have no other choice or way to bypass iterative (interactive and incremental) prototyping if you are not magician