Design Question - InfoPath Dev
in

InfoPath Dev

Design Question

Last post 05-11-2009 03:30 AM by mbrady1973. 6 replies.
Page 1 of 1 (7 items)
Sort Posts: Previous Next
  • 05-09-2009 07:07 PM

    Design Question

    Hello,

     

    I have created a couple of forms that query SQL data and present it. Fairly straight-forward. What I am looking to do is create an employee evaluaton form and submit the results back to SQL database.

    I can't figure the steps out??

    Do I...

     1. Design Database in SQL then desighn the form?

    2. Design the form first, then design the database?

     Also, in the evaluation, I need to add radio buttons, with a textbox that averages the values of the radio buttons. How do I get those values to SQL?

     

    Thanks

     

      Very confused and quite a newbie.

  • 05-10-2009 01:02 AM In reply to

    Hi mbrady1973 and welcome,

    It will be much easier to create the SQL database first then create the InfoPath forms. This will give you the ability to reference th SQL database in InfoPath as a DataSource. Then you can easily drag and drop fields from the datasource onto your design area.

    "Also, in the evaluation, I need to add radio buttons, with a textbox that averages the values of the radio buttons. How do I get those values to SQL"

    Can you give an example?

    - Samir -

  • 05-10-2009 03:56 AM In reply to

    Thanks for responding Samir.

    So, for the Database: I should draw my plan and create the database?  Is there any special considerations that I should give to field sizes etc., in the database?

    Now for the radio buttons.

    • I don't understand what type of fields to ceate in SQL, and I want to make sure that each button that is clicked will be able to be submitted numerically back to the SQL database.
    • I also am confused as to how to create a formula that averages the section of radio buttons.

    I hope this makes sense?

    There is a great sample of what I am trying to do in the samples section of Infopath 2003. It is called "Applicant Rating". Although it is not exact, the radio button area is similar to what I am trying to accomplish.

  • 05-10-2009 10:28 AM In reply to

    Hey mbrady1973,

    For the radiobuttons, I suggest making their value an integer, and saving that integer to the database (tinyint). This is due to the fact that normally a person can just choose one radiobutton option.

    "Is there any special considerations that I should give to field sizes etc., in the database?"

    Not that I know of.

    Hope this helps,

    - Samir -

  • 05-10-2009 08:34 PM In reply to

    OK, every time I try to create a table to house my radio buttons, it turns into a repeating table. Is this normal? It seems to be ruining the format of the table. Any suggestions.

  • 05-10-2009 10:40 PM In reply to

    What are the steps you have taken that lead to producing this behavior?

  • 05-11-2009 03:30 AM In reply to

    Thanks again for your time.

     Steps:

    1. New project connecting to database I created
    2. Now I am at a new form to design with my fields in the taskbar (Query and Data Fields)
    3. (This is where it starts getting confusing)
    4. I am now looking at the title section. Below that is the new record button,below that is the "drag query fields" section, below that is the 'run query button, and below that is the 'drag data fields' section.
    5. Now, I try to insert a 2-column table under the 'New Record Button'. This is for basic info, Name, Date etc.
    6. Next I insert a 'layout table' for my radio buttons. When I insert the radio buttons from the 'data fields' section it only give the option for 'repeating' option button. This is where it takes my nice table and heighten the rows substantially. Also, I don't think I want this as 'repeating'.

     

    Should I be formatting the page differently at start, or is there anything you can see that I am doing wrong. Again, seems pretty simple, yet it is really throwing me for a loop.

Page 1 of 1 (7 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.