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

Lists behaving badly...

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

    Lists behaving badly...

    I have UX that uses list controls and i have multi-generational lists. My Grand Parent list is a Customer Table, my Parent List is a Header Table, which is really a project summary, and I have multiple child lists. Each child list contains data on different parts of the project, ie, windows, doors, roofs, etc.

    This is meant to be a disconnect app.

    In my testing and teaching myself Alpha I decided to use just three lists on the UX, one from each generation - finally everything was working great. Then I decided to add a couple more of the child lists and put them on my UX. This is when things starting acting funny. When add I new records to the child lists they get assigned to the parent, and grand parent but in addition there's a new parent record created. The new parent record does not reference back to the child, it's just an empty record in the table.

    Any idea what can be causing this?

    #2
    Re: Lists behaving badly...

    Am I the only person having problems like this???



    Originally posted by PhotoHog View Post
    I have UX that uses list controls and i have multi-generational lists. My Grand Parent list is a Customer Table, my Parent List is a Header Table, which is really a project summary, and I have multiple child lists. Each child list contains data on different parts of the project, ie, windows, doors, roofs, etc.

    This is meant to be a disconnect app.

    In my testing and teaching myself Alpha I decided to use just three lists on the UX, one from each generation - finally everything was working great. Then I decided to add a couple more of the child lists and put them on my UX. This is when things starting acting funny. When add I new records to the child lists they get assigned to the parent, and grand parent but in addition there's a new parent record created. The new parent record does not reference back to the child, it's just an empty record in the table.

    Any idea what can be causing this?

    Comment


      #3
      Re: Lists behaving badly...

      Are you sure a "LIST" control is what you should be using? I'm thinking this sounds like something for Repeating Sections.

      If it is even possible to do this with LIST controls then my guess would be that the primary keys are not set up quite right for Alpha or that alpha is not bound quite right to the primary keys. Make sure each primary key is composed of a single identity field - either numeric ID or GUID. If using a backend DB then let it assign the ID and make sure you app isn't also trying to assign it.

      Perhaps if you start the problem from scratch and a new NG thread and describe the keys and database and details about what level of repeating sections / tables does the code break then someone might have better guess.

      Comment

      Working...
      X