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

Some design suggestions please.

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

  • Some design suggestions please.

    I have V11 and V12 but I've been using V11 exclusivley. I have a small project where I'd now like to use V12 to get my feet wet and I'd like some advice on how to proceed. It needs to be easy and fast to enter the data so a checkbox instead of a drop-down, things like that.

    The project pretty much takes a paper form and allows the user to fill it out on-screen. The paper form has familiar fields some of which include:

    Date Entered
    Date Called
    First Name
    Last Name
    Address
    Phone
    Q1 Y/N
    Q2 Y/N
    Q3 Y/N
    ...
    Employee Y/N
    Contractor Y/N
    ...
    $ Compensation, Tips etc
    Q4 Y/N Explain
    Q5 Y/N Explain
    Q6 Y/N Explain
    ...
    Notes Field.


    Each record will be saved as its own record. IE: There will not be a Employee table where the user can choose from a list, the employee details will be filled in each time. Pretty much flat file. This is a legal requirement. I may be able to change some of that down the road but for right now that's how it is.

    I'm pretty sure I should use a UX component, maybe make it look similar to the form and let them fill it out.

    I have already created a table with the fields I need.

    Is a UX the best way to go?
    As I've already created a table I don't want to have to enter all those fields again on the UX so is it possible to have the UX get the fields from the table?
    There are roughly 5 different areas, ie: Personal, Employment, Health etc so maybe tabs? or just one form and have them scroll?
    Is it possible for the UX to adjust to the size of the users monitor? For instance, using % instead of fixed length?

    I don't know what else to ask because although I keep paying for V12 I've never actually used it! This is the project I'm hoping will give me a push.

    Thanks for any help you can provide.

    -John

  • #2
    Re: Some design suggestions please.

    Yes... a UX will be a very good place to start... and it's fairly easy to work with. Web or Mobile?

    You can, if you want to, get your UX to actually look like your paper form by having that form be a background image.

    Videos for this can be found within Alpha using Help, Video Finder. Videos UX_V12--81 and UX_V12--96.

    As I've already created a table I don't want to have to enter all those fields again on the UX so is it possible to have the UX get the fields from the table?
    Yes... in your UX, add a Control... and in the popup dialog to enter that control there is a link at the bottom... Populate list from a table.

    There are roughly 5 different areas, ie: Personal, Employment, Health etc so maybe tabs? or just one form and have them scroll?
    The UX Tab Control sounds like a good idea.

    Is it possible for the UX to adjust to the size of the users monitor? For instance, using % instead of fixed length?
    Yes... % can be used.

    Just jump in... there will be lots to drive you nuts... but stick with it and post questions... it'll be worth it.
    There is a nice Switch Control for your Y/N fields.

    Comment


    • #3
      Re: Some design suggestions please.

      With regard to the Employees data, you can save each employees' data to a "lookup" file, and allow the employees to choose their name from that file, thereby populating the new record without the need to have redundant information re-entered every time.
      You could write the records to the lookup table in the AfterValidate event when the employee enters their info the first time. After that, the script could query the lookup table and not write the record unless the data changes (much like QuickBooks asks if you want to save the changed data to customer file, for example).
      Jay Talbott
      Lexington, KY

      Comment


      • #4
        Re: Some design suggestions please.

        As I've already created a table I don't want to have to enter all those fields again on the UX so is it possible to have the UX get the fields from the table?

        Alpha helps with this.message board answer.png

        Comment


        • #5
          Re: Some design suggestions please.

          Hello again,

          I want to thank you for all the advice, a little late but thanks! :)

          -John

          Comment

          Working...
          X