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

Record number skips at Set level, quirky

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

  • Record number skips at Set level, quirky

    I have a "Header" table with 3 records, when I look at them in the table level they are Record Number 1-2-3 on the toolbar on top, scrolling back and forth is fine, and the browse are fine....

    When I try at the Set level, (this is the parent table and I have the index at record number, also I just repacked and rebuilt indexes), record two skips over... ie 1-3 3-1 when using the for record numbers... if I put the number 2 in the record number field, I will get a lockup...

    No field level events are going on, and this occurs.
    The Form events are quite benign (setting a variable "mode"
    and maximizing the window) and I temporarily took out the cross file validations just to eliminate another factor..

    I also tried duplicating and renaming the table..
    (and the child browse set is empty, no issues there)

    Any idea why this behaviour should be quirky ?


    ============================================================
    (I was having one or two other weirdnesses also, such as a record repeating 3 times in the set browse mode but that fixed after the pack/reindex)

  • #2
    RE: Record number skips at Set level, quirky

    You'd have to send your set to us. My only thought is that you have a one-to-many relationship with no child records, which would cause the set to browse at a different level. In that case, it isn't quirky or inconsistent, it is behaving as it should. But...we'd have to see your data to be sure.
    Aaron Brown
    Alpha Software Development Team

    Comment


    • #3
      RE: Record number skips at Set level, quirky

      Steven,

      Consider posting a copy of the entire database here, so we can look at it.

      I'm puzzled (and a little alarmed) that you actually have a field in your table called Record Number. Did you build an index on it, and what did you call it?

      Windows requires all objects in a program to be separately named. You can get into trouble if you start naming things with names that match internal names used by Alpha Five. I don't know for a fact that 'Record Number' is a reserved word, but I would NOT be surprised. I'm wondering if Alpha Five is getting confused with your index arrangement. There's no need to create an index based on each records' 'record number' in order to view them in record number order. -- tom

      Comment


      • #4
        RE: Record number skips at Set level, quirky

        Tom Cone Jr
        I'm puzzled (and a little alarmed) that you actually have a field in your table called Record Number. Did you build an index on it, and what did you call it?

        Steven
        :-) No, what I meant was that when you go into Menu/Query/Select Index or Query--
        There are four choices, the 3 indexes and one called

        And that the one that is "Active" is

        =====================================================
        Aaron Brown
        You'd have to send your set to us. My only thought is that you have a one-to-many relationship with no child records, which would cause the set to browse at a different level.

        Steven
        Okay,I may have an Alpha Users Group meeting tonite (NYC) and I will see if there is way to load it there and show it live, if not I will plan to zip it up tonite or tomorrow

        Keep in mind that this quirky missing record is at the parent level.. and I am comparing the forms for the table and the set to see the record numbers, and the set is losing one record...
        (the browses are simply a confirmation, and also at the parent level)

        I know a lot of newbies are not really programmer lingo savvy but I have many years of mini-computer background and did some Alpha 4 stuff years back, so I am trying to double and triple check any problem or question before posting it here....

        Thanks for the help, this is my most important issue right now :-)

        Comment


        • #5
          RE: Record number skips at Set level, quirky

          Does it do this in the default form for the set???
          If you're not sure what that is, under tables sets tab, simply double click the set.
          If it doesn't happen there, but does do it in a custom form, check out that form's properties and if you have anything in filter or order, erase it and try again.
          If it does, is there a browse on the form for the child records, or do you have the child fields on the form itself, but not in a browse?

          Comment


          • #6
            RE: Record number skips at Set level, quirky

            John Zaleski
            Does it do this in the default form for the set???

            Steven
            Good suggestion..

            Yes, I should have mentioned that ...
            It does also occur at the default form of the set...
            The record is missing in record mode and in the browse..

            .. but, it gives us more information...
            a message rather than locking up...

            "Cannot go to record two because it is not part of the current query, or that record may have been deleted"
            "Click the 'Show All' button to turn off the current query, then try again"

            The 'Show All' button under query is grayed out, I hadn't done any querys ...

            And I am not supposed to have any deleted records, as shown in the table default form ... so it seems to be a "pseudo-deleted" record ? hmmm.. (remember I just packed the table to be sure)

            I remember back when I first played with .dbf files, I was never real happy with the language-given deletes, so I would sometimes emulate them with a "delete code" (giving a little more control eg. if you want to keep the deleted records in an auxiliary delete history file).

            Ok.. I will poke around a little more, consider .zip the file up later, bringing it to the User Group meeting now.

            ( and.. shhh.. also consider adding my own delete code and disabling the systems, at least on a couple of vital tables)
            =================================================

            John
            If it does, is there a browse on the form for the child records, or do you have the child fields on the form itself, but not in a browse?

            Steven
            There was a browse for the one-to-many child records, none on the form itself..

            Steven
            Thanks.. good suggestion above. "why didn't I try that out more carefully myself" :-) Still a problem, maybe a real glitch, but focused now to know exactly what the super-techies can look for..

            Comment


            • #7
              RE: Record number skips at Set level, quirky

              Aaron Brown
              You'd have to send your set to us.

              Tom Cone Jr
              Consider posting a copy of the entire database here, so we can look at it.
              =================================================
              Steven

              Ok, ready for that, since I duplicated the problem on a fresh set of data, even on the very first record...
              but the earlier 3 record data is the best for looking..
              (The second record shows up in the table but not the set view)

              ============
              Actual Application 5 meg Zip 800 K
              Streamlined Version 1 meg 150 k
              (this includes the form that created the problem)
              ============
              arival.sem 292K - arival is the set with problem
              container_hdr.ddm 29Ok - the parent table of arival with the problem
              ===========================================

              Here are instructions..

              1) Look at container_hdr in default browse and notice the three records, Record #2, Container ABC1234 is the issue

              2) Look at the Arival Set and notice that it goes from record 1 to record 3, if you handput record #2 in the toolbar you will get the message I mentioned above (about query and delete)

              3) The Arival Form is available, it acts similarly to the Arival Set (it used to lock up, now it gives the same msg as above, probably because I cleanup up some code, however in the new database the same problem locks up Alpha, probably because it is in record #1)

              Thanks :-)
              This is really my one big hindrance now ...

              Comment


              • #8
                RE: Record number skips at Set level, quirky

                Aaron Brown
                You'd have to send your set to us.

                Tom Cone Jr
                Consider posting a copy of the entire database here, so we can look at it.
                =================================================
                Steven

                Ok, ready for that, since I duplicated the problem on a fresh set of data, even on the very first record...
                but the earlier 3 record data is the best for looking..
                (The second record shows up in the table but not the set view)

                ============
                Actual Application 5 meg Zip 800 K
                Streamlined Version 1 meg 150 k
                (this includes the form that created the problem)
                ============
                arival.sem 292K - arival is the set with problem
                container_hdr.ddm 29Ok - the parent table of arival with the problem
                ===========================================

                Here are instructions..

                1) Look at container_hdr in default browse and notice the three records, Record #2, Container ABC1234 is the issue

                2) Look at the Arival Set and notice that it goes from record 1 to record 3, if you handput record #2 in the toolbar you will get the message I mentioned above (about query and delete)

                3) The Arival Form is available, it acts similarly to the Arival Set (it used to lock up, now it gives the same msg as above, probably because I cleanup up some code, however in the new database the same problem locks up Alpha, probably because it is in record #1)

                Thanks :-)
                This is really my one big hindrance now ...

                The Application is called Invoice
                The Zip file is dummy.zip

                Comment


                • #9
                  RE: Record number skips at Set level, quirky

                  Aaron Brown
                  You'd have to send your set to us.

                  Tom Cone Jr
                  Consider posting a copy of the entire database here, so we can look at it.
                  =================================================
                  Steven

                  Ok, ready for that, since I duplicated the problem on a fresh set of data, even on the very first record...
                  but the earlier 3 record data is the best for looking..
                  (The second record shows up in the table but not the set view)

                  ============
                  Actual Application 5 meg Zip 800 K
                  Streamlined Version 1 meg 150 k
                  (this includes the form that created the problem)
                  ============
                  arival.sem 292K - arival is the set with problem
                  container_hdr.ddm 29Ok - the parent table of arival with the problem
                  ===========================================

                  Here are instructions..

                  1) Look at container_hdr in default browse and notice the three records, Record #2, Container ABC1234 is the issue

                  2) Look at the Arival Set and notice that it goes from record 1 to record 3, if you handput record #2 in the toolbar you will get the message I mentioned above (about query and delete)

                  3) The Arival Form is available, it acts similarly to the Arival Set (it used to lock up, now it gives the same msg as above, probably because I cleanup up some code, however in the new database the same problem locks up Alpha, probably because it is in record #1)

                  Thanks :-)
                  This is really my one big hindrance now ...

                  The Application is called Invoice
                  The Zip file is Invoice.zip

                  Comment


                  • #10
                    RE: Record number skips at Set level, quirky

                    The problem is in your set structure...

                    You have a one-to-one link from CONTAINER_HDR-TYPES that has its "Include record in parent table" property set to "Only if a matching child record DOES exist." Change this rule and it works fine.
                    Aaron Brown
                    Alpha Software Development Team

                    Comment


                    • #11
                      RE: Record number skips at Set level, quirky

                      Perhaps I should be more clear.

                      In looking at your data, the linking key between Container_Hdr and Types defined as an expression. You don't have a record in Container_Hdr with a matching linking key in Types. The problem will also go away if you give one of the records in container_hdr a matching linking key.
                      Aaron Brown
                      Alpha Software Development Team

                      Comment


                      • #12
                        RE: Record number skips at Set level, quirky

                        Hi,

                        Thanks so much Aaron, now I can keep on moving along !

                        I must have been in a fog when I did that link :-)
                        Probably didn't notice that it was a limitation no
                        the parent table...

                        Took out the requirement..

                        Kudos for the quick find..
                        =============================================

                        Comment

                        Working...
                        X