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

A tab too far

  • Filter
  • Time
  • Show
Clear All
new posts

    A tab too far

    I can't code worth a damn. Problem: Tabbing past the last tab stop on my form causes multiple invalid records in a child table.
    Form-frm_svcorderentry1 based on table.
    Trace: Created by just tabbing through the order.

    Event: :frm_svcorderentry1 "OnActivate"
    Event: :frm_svcorderentry1:Save "CanArrive"
    Event: :frm_svcorderentry1:MEMO "CanDepart"
    Event: :frm_svcorderentry1:MEMO "OnDepart"
    Event: :frm_svcorderentry1:Save "OnArrive"
    Event: :frm_svcorderentry1:Cancel "CanArrive"
    Event: :frm_svcorderentry1:Save "CanDepart"
    Event: :frm_svcorderentry1:Save "OnDepart"
    Event: :frm_svcorderentry1:Cancel "OnArrive"
    Event: :frm_svcorderentry1:HOW_MANY "CanArrive"
    Event: :frm_svcorderentry1 "CanSave"
    Event: :frm_svcorderentry1:Cancel "CanDepart"
    Event: :frm_svcorderentry1:Cancel "OnDepart"
    Event: Table( TBL_JOBSDETAIL ) "CanSaveRecord"
    Event: Table( TBL_JOBSDETAIL ) "OnSaveRecord"
    Event: :frm_svcorderentry1:Cancel "OnArrive"
    Event: :frm_svcorderentry1 "OnSave"
    Event: :frm_svcorderentry1:Cancel "CanDepart"
    Event: :frm_svcorderentry1:Cancel "OnDepart"
    Event: Field( TBL_JOBSDETAIL->HOW_MANY ) "CanEditField"
    Event: Field( TBL_JOBSDETAIL->HOW_MANY ) "OnEditField"
    Event: :frm_svcorderentry1:HOW_MANY "OnArrive"
    Event: :frm_svcorderentry1:HOW_MANY "CanDepart"
    Event: :frm_svcorderentry1:HOW_MANY "OnDepart"
    Event: Field( TBL_JOBSDETAIL->HOW_MANY ) "CanEditField"
    Event: Field( TBL_JOBSDETAIL->HOW_MANY ) "OnEditField"
    Event: :frm_svcorderentry1:HOW_MANY "OnArrive"
    Event: :frm_svcorderentry1:HOW_MANY "CanDepart"
    Event: :frm_svcorderentry1:HOW_MANY "OnDepart"
    Event: Table( TBL_JOBSDETAIL ) "CanEnterRecord"
    Event: Table( TBL_JOBSDETAIL ) "OnEnterRecord"
    Event: :frm_svcorderentry1 "OnEnter"
    Event: :frm_svcorderentry1:HOW_MANY "CanArrive"
    Event: Field( TBL_JOBSDETAIL->HOW_MANY ) "CanEditField"
    Event: Field( TBL_JOBSDETAIL->HOW_MANY ) "OnEditField"
    Event: :frm_svcorderentry1:HOW_MANY "OnArrive"
    Event: :frm_svcorderentry1 "OnDeactivate"

    How to generate problem:
    Open From: frm_openjobs 'Based on set set_jobentry
    On browse of form: Double-click any parent record. 'The onrowdoubleclick envent of the browse will open the frm_svcorderentry1 form, creat a new child record, and populate several fields.
    There are only five tab stop fields. If the user tabs past the last tab stop "5" three ugly and unwanted records are created in the tbl_jobsdetail.
    I either want to prohit the user from tabbing past the last tab stop or allow the tab stop without the mess.

    Please help!

    RE: A tab too far


    Using Vers 4.5 I don't get multiple new records in the job_details table.

    However, if the user tabs through the last field (in tab order) Alpha Five saves the current record and begins a new one. This is normal and is symptomatic of 'continuous data entry'.

    One solution to this is to place a dummy button on your form. Put a short one line script in it's OnArrive event, to activate another field on the form. As soon as focus arrives at the dummy button, it's passed back to another field on the form, you see? If you then arrange for this dummy button to be 'last' in tab order, the tab key can never be used to tab OUT of the 'last' field. (As soon as focus arrives there, your script kicks focus to the field you specified...) You can set the properties of the button so that it's hidden, so the user won't be aware of what's happening. Perhaps others will have a better solution, but this works for me.

    I noticed in passing that your set uses referential integrity, and that your frm_openjobs form incorporates a named browse. My personal preference is to use embedded browses in situations such as this, and to avoid using referential integrity in the set specifications. I find embedded browses simpler to work with, and I'm not smart enough to understand all the possible ramifications of how referential intergrity works.

    -- tom


      RE: A tab too far


      Thank you very much. Sometimes the simplest of things elude me. I prefer to use the referential integrity to simplify deletion of records once the job has been completed. I have found that entering child records based on a child table does not provide referential integrity. I suppose that each parent/child relationship must be stored in one of the set index files. Idunno. Anyway, I can press on thanks to your help.