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



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

Opinions on Form Design change

  • Filter
  • Time
  • Show
Clear All
new posts

  • Opinions on Form Design change

    I have a rather complex form where data entry takes place at the child and grandchild levels and it uses several conditional objects to show or hide sections of the form's tables until some pertinent data is filled in. The problem I am having with this form is that currently it runs filtered by a query that seems to be what may be messing with the updating of the child table indexes. So I am trying to get rid of the need for this query as the means to show the linked records for a particular date.

    One of the things I am trying out is to have a one record table (SCHEDHDR) with one field (SCHEDATE) as the header for the set. I want to initially open the form to today's date which most often will not have any linked records yet. But I also want the option to let the user pick a previous or future date from the calendar smart field and have the set links refresh. Which doesn't work directly just by changing the header date, so I recall the form in the schedate field's OnChange event and that seems to work - so far.

    In the original design, I used a shared variable on the form to change the date and refresh the query. But if the user moved to a date without links the conditional objects would still display briefly or when adding multiple new child records, the query would get out of synch and the only fix was to close and reopen the form.

    The other idea I tried was to prepopulate the SCHEDHDR table with business days. But that is also fraught with problems if new header dates are needed.

    Changing the set header link field and recalling the form in that one place seems the easiest way to simplify this form. Is anyone else doing this OR has abandoned this idea? It would be good to know the reasons before I tackle changing a bunch of scripts...

    Last edited by MoGrace; 11-17-2018, 08:36 PM.

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

  • #2
    Re: Opinions on Form Design change

    One thing I just discovered with this new set is that I am not getting the correct record pointer for the appt_hdr table that is displayed in an embedded browse, but also has some fields pulled out on the form. When I try to reference those fields from the selected browse row, I am getting data from the top record in the browse and not the one I am on.

    Why is it doing this? Or better yet, how do I fix it? I need the info from the current record to use in a script that adds another record in an external table.

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford


    • #3
      Re: Opinions on Form Design change

      Finally found the answer HERE The trick is to set the pointer to the browse table and not the set table.

      Doesn't work: hdr = table.current(2) -> always points to first record displayed in the browse

      This works: hdr = browse1.table_get() -> points to the selected record

      Apparently none of the 60+ people who viewed this thread knew the answer either! Hope it helps some of them...

      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford


      • #4
        Re: Opinions on Form Design change

        I believe you might know my answer... perform all data entries using xdialogs. They offer complete and total control of data presentation and data processing, unencumbered by a base table connection to mess you up and having a table(s) held open because of the form-table requirement, complete control of data entry events for presentation of secondary data, and objects showing data, or for data entry, and ease of presentation of data not within the set which a form is obligatorily bound to ... dialogs are THE ticket for exquisitely fine-tuned data review and data entry processes. It is a very rare instance I use a form for data entry and I use dialogs routinely for presentation of data from mild-to-moderately complex data mining. High complexity data mining goes to temporary tables and are presented in reports linked to the temporary tables. This business needs magic and xdialogs allow you to make magic.
        Mike W
        "I rebel in at least small things to express to the world that I have not completely surrendered"