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

A5 forces wrong index ?

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

    A5 forces wrong index ?

    This application uses a concatinated key, SYSTEMNO + DHI. Have setup primary index as SYS_DHI. A5 has also setup DHI as an index and appears to default to it. Have tried deleting it but A5 sets it back up again. Have tried moving it to the second listed index, A5 puts it first again. Needless to say any repeating values of DHI alone will not process in my append operations. The application does not use any scripts or xbasic. KISS method. Any thoughts would be appreciated.
    John
    Tags: None
    #2
    RE: A5 forces wrong index ?

    When rebuilding indexes A5 puts them in alphjabetical order.

    Sounds like index might be used in set relationship as likning index. Confirm that DHI is not used in set or defined separately unlesds you want it.

    Otherwise just select index ( [Ctrl][I] ) to set index and it should be the "default" injdex until you choose another.

    If this doesn't work or address the issue then maybe I'm not understanding you. Will try to get back on lateer today and check your response.

    Comment

      #3
      RE: A5 forces wrong index ?

      Alpha Five will create indexes needed because of your design, if they don't already exist. The index 'last used' for a table or set, will often continue to be the default until the user changes to another, or exits Alpha Five altogether.

      Tell us more about the context in which this is happening. In the meantime, use Ctrl-I to switch when to another index when desired.

      Also, you might consider setting the 'order' property of your forms. Doing so will assure that the proper index is always primary when a form loads.

      Comment

        #4
        RE: A5 forces wrong index ?

        Tom & Jim
        Have searched all related dbf's & sets, cannot find a DHI only index reference. Unfortunately these are operations (join & append) not forms. Have also noticed that a related form displays the records in DHI order despite having the order set to SYSTEMNO + DHI, unless I set the index prior to opening. Any way of id'ing where A5 might be getting this DHI only referennce.

        Operation 1.
        Join DHI table (index SYSNO) + Sysno table (index SYSNO) = HS_MAS_T (result table). Works OK.

        Operation 2.
        Append Master HSMASTER (index & link key HSSYSTEMNO +DHI), from Transaction HS_MAS_T (link key HSSYSTEMNO + DHI). (HSSYSTEMNO is a different field than SYSTEMNO).This operation appears to consider DHI only & not add what it thinks are duplicate records. This applies even if I set the index just prior to running.

        Operation 3.
        Append Master HSDETAIL (index & link key HSSYSTENO + DHI), from Transaction HS_MAS_T (link key HSSYSTEM + DHI). Works OK!

        Note: The result will be a set with HSMASTER being the parent & HSDETAIL being the child. This will create only the 1 st child record with subsequent children being added manually through the set using the approprite form. This form also has the same problem if I try to add a new parent with the same DHI (But a different SYSTEMNO) ERROR: Values for this field must be unique DHI.

        Table HS_MAS_T is not indexed despite having been defined as indexed (because of join ?) and another field in the result table is missing. It is Id'd in table definition but not filled in by join (field not from either tables used in join). Clear as mud ?.
        John

        Comment

          #5
          RE: A5 forces wrong index ?

          I'm having trouble with all the similarly named objects in your system.

          Is there some reason you can't delete the offending index and then run each operation one at a time, checking the appropriate table's index list after each operation?

          Comment

            #6
            RE: A5 forces wrong index ?

            Tom
            When I delete an index, close and reenter define indexes the index has re-created itself ?

            Comment

              #7
              RE: A5 forces wrong index ?

              that hints strongly of a script running when your database loads or when your first form opens... and said script asks Alpha Five to arrange the sequence in such a way that an index is generated. Check your autoexec script and any onInit or OnActivate scripts associated with the forms you are opening.

              If that doesn't get it, I suggest zip it all up and let us take a look at it.

              Comment

                #8
                RE: A5 forces wrong index ?

                Tom
                Have no scripts or xbasic that I know of. Have Zipped up reduced system including "TOM read me first" not sure how to attach file. will try
                Thanks John

                Comment

                  #9
                  RE: A5 forces wrong index ?

                  Tom
                  File size exeeded 1 MB. Aborted. Will try & reduce
                  John

                  Comment

                    #10
                    RE: A5 forces wrong index ?

                    There also might be a field rule such as a validation specifying unique or cross file that causes alpha to recreate the index tag. To test this you might leave the "DHI" index tag but change it to something else ( date field or other ). When you enter the form Alpha will probably create the same index only DHI_1 or something. Or make a copy of the database and delete all field rules and see if index gets recreated.

                    Comment

                      #11
                      RE: A5 forces wrong index ?

                      Tom
                      Reduced file on its way
                      John

                      Comment

                        #12
                        RE: A5 forces wrong index ?

                        John, Tom, Jim
                        John
                        You hit the nail on the head. Had a field rule defining DHI as unique. Removed and it ran perfectly. Once again the forest for the trees. Has had me going for 2-3 weeks.
                        Thanks VERY much. Once again the board and its supporters to the rescue. Tom if you have a minute to look at the "TOM read me file I had a few other questions.
                        THANK YOU ALL
                        John

                        Comment

                        Previous template Next
                        Working...
                        X