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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Alpha Sports Invoice Screen: a5_scrollarea1() & Associated Coding Problems?????

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Alpha Sports Invoice Screen: a5_scrollarea1() & Associated Coding Problems?????

    How is this created? What is it? And doesn't it create a significant programming issue?

    If you take a look at the Xbasic explorer with the Invoice form running the addressing of many fields appears to change, as an a5_scrollarea1 object is added to the forms object.....

    Many of the forms objects are listed (nested) under this object in view mode: a5_scrollarea1
    When you return the form into edit mode, this object disappears & the objects are displayed right below "topparent."

    For example, check out the the invoice2 field of Alpha Sports....

    First, when the Invoice is in (View mode): (both Object explorer & Xbasic explorer) you get to the object as follows: (by either dragging & dropping from the XE, or copying to clipboard from the OE)
    ?Invoice:a5_scrollarea1:invoice2.value (results as entered into the IW)
    = "000007"

    But, when the Invoice form is in (Edit mode): (both Object explorer & Xbasic explorer) you get to the object like this: (again, by dragging & dropping from the XE, or copying to clipboard from the OE)
    ?I:Invoice:Invoice2.value (again results as entered into the IW)
    = "000007"

    If you try to access the properties in the wrong mode, you get errors..... Alas....

    Won't this break code when attempting to address to these objects by using these tools when coding? (relative versus explicit, or partial etc. addresses are all different....???? Even worse, how about using this format for addressing the object: topparent:A5_scrollarea1:Invoice2.value versus topparent:Invoice2.value????

    ~Obviously, depending upon mode (form edit / form view), the code used to address the object is different!

    Also, is it just me, or wouldn't it be a smart idea to have access to the Xbasic Explorer when editing action scripts that have been converted to "in-line Xbasic code?" .....As it is now, it's right there in the RH docked panel, but because the editing screen (for converted in-line Xbasic) is modal, you can't get to the tool to drag & drop properly formatted code...... I frequently convert action-scripts to "tweak them" and am very frustrated that this "core" a5 coding tool is unavailable here. ~ It sure would help me avoid some "simple" mistakes and save time too!
    Last edited by SNusa; 06-12-2011, 04:54 PM.
    Robert T. ~ "I enjoy manipulating data... just not my data."
    It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
    RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."
    Tags: None
    #2
    Re: Alpha Sports Invoice Screen: a5_scrollarea1() & Associated Coding Problems?????

    I use xbasic explorer and object explorer a lot. But only when working with the form layout in design mode. Could be wrong, but I do not think they were intended to be used while the user is editing records through the open form.

    Comment

      #3
      Re: Alpha Sports Invoice Screen: a5_scrollarea1() & Associated Coding Problems?????

      Originally posted by Tom Cone Jr View Post
      I use xbasic explorer and object explorer a lot. But only when working with the form layout in design mode. Could be wrong, but I do not think they were intended to be used while the user is editing records through the open form.
      Your response makes sense. But the reason I ended up here, using the form in view mode goes back to the .value & .text properties.....
      The only way I've been able to tell where and when the .text and .value properties both actually have values that correctly reflect what is displayed on a form is by having the form in view mode. (and checking for property values via drag & drop from the XE)....

      It's also how I've been able to test for / debug "broken" action script code.

      Because when in "edit mode" the .text value does not resolve to the same "value" it would when the form is in view mode.
      (Hence, to test for this, the form needs to be in view mode.)
      Robert T. ~ "I enjoy manipulating data... just not my data."
      It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
      RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

      Comment

      Previous template Next
      Working...
      X