InfoPath Dev

What were you doing when you got the unable to connect? What were you trying to do?

The trick is to check this while you are in the install process. Once you get through to where you configure the database, look in IIS and access the web config which should be there at this point before the roll back. Also make sure your account you are using has permission to create databases and a QdabraDBXL db is being created.

If you have no existing field, then I would add a field, which is false by default but when the form is submitted is set to true.  Then in the open rules if field is true switch views.

Welcome Steven, to the forum and InfoPath development. I have done several conversions from Access Forms to InfoPath. Once you understand InfoPath it is a much faster and easier medium to build forms in and is much more capable then Access with improved features. However I prefer to use SQL or SQL Express on the backend since they are more ...

Hey there. You have run into one of the limitations of the Database type form.  You can only query and submit one table structure, you are bound to certain table relationships, and an insert adds all tables or the whole structure. You either need top create new seperate forms for the seperate tables or use web services. Typically we use ...

This is simple to do but you need all of the information. You would need to identify the form user. Then whether they are a manager. And then add conditional formatting to the form to hise the section or have a seperate view, which ever is appropriate. You may be interested in the Database Accelerator to keep a list of managers or in the ...

You would need a second view which is read-only or what ever you wanted. Then you need a field in your form to track the state of the form, submitted or not.  There may also be a field which would be blank on a new form and has a value after submit, this would work for detecting whether the form was new or submitted. Once you have your ...

I just realized you may be referring to the submit button in the toolbar.  I do not think you can effect it dynamically.  The solution is to go into the submit properties and permanently remove the submit from the tool bar and just use a button in your form which you can control as described above.

If you go into button properties. To the display tab and then Conditional Formatting. You can add conditions and have the result be to either hide the button or disable it when the conditions are true.

Hey There. For number one I would use another field as a counter.  Have it reset on each open or for each unique user. Use a rule on insert that increments it (could be a true or false too) and then put conditional formating so that if the counter has been incremented or changed do not allow additional inserts. For ...