Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Looking for ideas/suggestions/pitfalls on a multiple fillable form scenario

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Looking for ideas/suggestions/pitfalls on a multiple fillable form scenario

    I am redoing an application in Alpha created in Visual FoxPro. The new application is "web based" (no mobile requirements). Part of the application consists of completing forms for a case. The forms are standard forms designed by an Agency that oversees them. From time to time, an updated version of the form can be released that perhaps adds a new field, removes a field, etc. So far I have not encountered a major overhaul for a particular form. There are 12 different forms to work with, each case can have a subset of the forms, and sometimes a case can have multiple instances of a single form as well. Along with collecting the information from the form, there are requirements to print the form and have it look as close as possible to the original agency developed form.

    The current application has a master "Forms" table that stores a record of a forms existence, a foreign key to the case the form belongs to, and a foreign key to a table that defines the fields within the form. This is mostly doable except when a new version of the form is released and you have to decide if you can fit the changes of that form within the current table or if you need to create an entire new table to collect the new form requirements. A maintenance nightmare!!!

    Along with the master "Forms" table is a series of tables for each form "Instance" that links to the master "Forms" database and contains a field for each piece of data to be collected on the form. As stated above, there could be forma_1 and forma_2, where a_1 was an older version adn a_2 is an updated version. There's no limit to the number of Instance tables that could be needed. A maintenance nightmare!!

    I'm looking for advice from anyone who has/had similar requirements as to how you addressed the challenges of making a Fillable forms application. I watched the video on Mobile App Framework Data Driven Forms and aside from that being a mobile solution doesn't seem to far off from what I'd like to do. I've also seen where others have used an Absolute Container solution.

    My goals for simplifying this project would be the following:
    1) A forms definition table. I'm not sure at this time how that plays into the multiple versions of a single form so that the application can be easily updateable whenever a new version of the form is released
    2) A forms instance table that ideally links to a "Form Definition" with a single field of json data that contains the name/value pairs for the fillable information on the form.
    3) An easy way to print a PDF for any form and honor the version that the form was created under. So older cases may have version abc of a form, but newer cases have version def.

    Any guidance that can make this process smoother and more adaptable to change would be greatly appreciated.

    Happy New Year to all.
    Jeremy

    #2
    Re: Looking for ideas/suggestions/pitfalls on a multiple fillable form scenario

    As for your printing to a pdf form, I think you want to do a fillable pdf.

    Look here:
    https://documentation.alphasoftware....20Function.xml

    Comment


      #3
      Re: Looking for ideas/suggestions/pitfalls on a multiple fillable form scenario

      I won't answer the PDF question, but you can do all kinds of things with reports or HTML templates. Now, as for dynamic forms, you can construct a data structure that has your parent record (such as date/time stamp, id, etc. - but simple), then have your form table, a form field table, and then a form data table. When you create a new record it creates all the necessary records (one for each field) in the form data table. You can create all of this yourself, or we can help you. We created our Dynamic Forms module for just such a purpose. It will save you a ton of time and is made to work in disconnected mode. You can also check into Transform. You will most likely need to customize any solution to fit exactly what you want to do.

      Comment

      Working...
      X