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

Please Explain

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

    Please Explain

    Would someone please explain what the Cust_id in this line represents. This
    is taken from the OnRowDblClick example on p75 of the Xbasic reference manual.

    cust_id = parent:browse1:cust_id.value

    Is Cust_id the linking field?

    This is my script. I get an error message,

    "parent:browse1:account_numbr not found"

    Account_numbr is my linking field.

    frm = :form.load("AcctAnalysis")
    account_numbr = parent:browse1:account_numbr.value
    frm.index_set("accountnumber")
    frm.find(AcctAnalysis)
    frm.activate()
    frm.close()

    Thanks,

    Kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    RE: Please Explain

    cust_id is probobly a variable

    you can only address fields that are on the form or browse using that type of syntax

    var->cnum=parentform:browse1:customer.value refers to a field on the browse

    use the explorer to view available fields - ps: note that you will sometimes name a field's title on a browse different from its actual name - and the title name may be what you have to use
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    Comment


      #3
      RE: Please Explain

      Kenn:

      The phrase "linking field" is usually applied to set linking and has no meaning here except in the broadest sense; i.e. you may use account_nmbr to link in a set but it has no bearing on whether your script will run or not.

      In the script your refer to cust_id is a variable that holds the value of the customer ID field in the browse that is part of a form that is used to open a different form ("Customer_dialog") in order to display the customer information.

      The script initially opens the second form in dialog mode, gets the cust_id from the browse (cust_id = parent:browse1:cust_id.value), then performs a find in the second form to locate the correct customer record, then shows it.

      In order for your script to work, your browse must be named browse1 (check the browse properties) and the account_numbr field must be in the browse in which you are double clicking. If both of these are already true, is it possible that you have changed the column heading in the browse to something like "Account"? It is the column heading label that determines the way the

      parentform:browse1:account_numbr.value

      syntax works so you would need

      account_numbr = parentform:browse1:account.value

      and if you are modeling your script on the one in the manual, the find line should be
      frm.find(Account_Number)

      Finian
      Finian

      Comment


        #4
        RE: Please Explain

        Martin, yes it is a variable.

        Finian, thank you for the detailed explanation. It is appreciated.

        kenn
        TYVM :) kenn

        Knowing what you can achieve will not become reality until you imagine and explore.

        Comment

        Working...
        X