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

Buggy Bug???

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

    Buggy Bug???

    Is this a bug; a change in A5's behavior or normal??

    The form on which the button is to be placed is based on the parent table of a set.

    I create a button to open a form and choose 'Show Only Records Where' button. In the lower box for choosing the linking field, I find that the linking field is duplicated 4 times, once for each table.

    Example: Linking field is Case_Numbr. I have a total of 4 tables and the drop down box shows:
    Case_Numbr
    Case_Numbr0
    Case_Numbr1
    Case_Numbr2
    Case_Numbr3

    This is true for all fields that have the same name but they're in different tables. I've not seen this before. Have I never noticed or does A5 get confused over same field names but in different tables? I know there's been an issue naming a date field DATE but this is a new one to me. I've read the manual and haven't found anything dealing with this.

    Thanks for the input,

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.
    Tags: None
    #2
    RE: Buggy Bug???

    Ken, when Alpha Five needs to keep track of multiple instances of the same object it often uses a naming system similar to what you describe. Are you saying that the button genie isn't opening the called form correctly? -- tom

    Comment

      #3
      RE: Buggy Bug???

      When I need to select the linking fields, I'm faced with Case_Numbr, Case_Numbr0,Case_Numbr1, Case_Numbr2, Case_Numbr3 and have no clue which one is for which table.

      I guess what puzzels me is that this has not occurred in my other applications.

      kenn
      TYVM :) kenn

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

      Comment

        #4
        RE: Buggy Bug???

        Hi Ken,

        My guess is that this isn't a bug. Alpha will show you the controls (usually fields) on the form. Remember that a controls name does NOT have to be the same a field name. During the building process you probably put this field on the form several times ( and may still have it on the form in several places) hence you will see the control name, controlName, controlName0, controlName1, etc for each instance of the control (that references a given field) on the form, even if they all reference a single field. Again, you are not looking at the fields, you are looking at the controls (that manytimes reference fields, but not necessarily) on the form.

        Good luck,
        Jim

        Comment

          #5
          RE: Buggy Bug???

          Yes, but when they're in different tables, the object name is preceeded with the table name. If I have a field CITY in Tbl1 and CITY in Tbl2 and put both fields on the form, the properties will show the fields as Tbl1->CITY and Tbl2->CITY

          kenn
          TYVM :) kenn

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

          Comment

            #6
            RE: Buggy Bug???

            Ken, each object on the form has an 'object name'. The object name never includes the source table's name.

            Each table field that is dropped on a form has properties. One of those properties is the source of the field. The source for the field includes the table name.

            Check the properties of a child table field in your form. You will see on the setup tab that each has both an object name and a field property.

            Drop multiple copies of the same field on the same form and check each object's name. Look familiar?

            Comment

              #7
              RE: Buggy Bug???

              Tom,

              Yes, I'm on your wave length. But the alias names..........

              kenn
              TYVM :) kenn

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

              Comment

                #8
                RE: Buggy Bug???

                Hi Ken,

                >>But the alias names..........

                No, you are not dealing with alias names here. Each control on a form has it's own name. A control is just a container. It can contain a fields value, a variable, etc. Each control has to have it's own distinct name. Now Alpha chooses the the name for you when you 'place' a field on a form (actually you are not placing a field on the form, you are placing a control that is bound to a field). If the same name is taken already Alpha begins the number suffix routine to make sure each has it's own unique name.

                In many other development environments, such as Delphi and VB, you place a control on the form. NOW you go to that control as specifically bind it to an actual table and field. Alpha's does this for us, making the process easier, but because of this its easy to loose the distinction between a control bound to a field object and the field object itself.

                Good luck,

                Jim

                Comment

                Previous template Next
                Working...
                X