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

List Detail Client Side Event Confusion

  • Filter
  • Time
  • Show
Clear All
new posts

  • List Detail Client Side Event Confusion

    I'm using 6699-5464 and am working on a FormView application with three lists, two of which have Detail Views. What I'm finding is that when I enter code into a client-side event in one list it also appears in the corresponding event in another list. Further, it seems that the "Detail View" events and "List" events within a given List get confused; sometimes an event will appear in one without appearing in the other, another time it won't.

    For example, if I enter code into, say, the "afterSynchronize" event in List3 (I thought this was a List event but it also appears in the Detail View event list) then it appears also in the events for List4, if I delete the code from List4 then it disappears from List3. My guess is that one of three things is happening: I am incorrect in my assumption that these events are specific to each List (unlikely), my whole component is farkled and I'm going to need to recreate it (most likely), or (drumroll) there is a problem with this build of Alpha (slightly more likely than "unlikely"). I will test this in the latest version, and probably will also try to create a stripped component to test, but trying to track down all these issues is getting tiring.

    Has anyone experienced anything like this before? Any information would be appreciated, I fear I'm going to have to recreate this component and I really don't want to unless I've exhausted all other options.

    Norman K

  • #2
    Hi Norman, I don't have a specific solution for you. However, I will note that we basically totally ditched formview and made our own version of it. Much more straight forward and reliable. We had TONS of issues with Formview and it was just too much. In very rare cicrumstances we will use a limited case where it fits the bill. If you would like an demo of a replacement for formview, just let me know.


    • #3
      Well, I'll keep that in mind, unfortunately right now I've got to get this mod finished. The event confusion issue seems to have resolved itself, somehow (perhaps a multiple component issue, don't know). So I forge ahead.

      I feel kind of awkward, after being away from these Boards for so long, to come back with a slew of issues but the app has been functioning well on 6699. All of a sudden my client asks for a major change and I'm in the weeds.

      Thanks WDS for your post, as I say, I'll keep what you say in mind.

      Norman K


      • #4
        Hi Normal, a quick final note. We have been relatively happy with version 6699. I wouldn't upgrade unless you absolutely must.


        • #5
          Understood; the irony (I think it would be classified as irony) is that for the mobile app I'm upgrading the latest build has (at least lately) not given me any issues. So I will continue to use that version just for this project (keeping 6699 in abeyance).

          But I agree with your overall point. I wouldn't dare use anything but 6699 for my client's "main" app.

          Thanks for the post.