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

Program runs in Ver 7 but not Ver 8

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

    Program runs in Ver 7 but not Ver 8

    I submitted this as a bug report back in December and have contacted Alpha but have not heard anything and was wondering if anyone could take a look and see if I have done something wrong. Thanks.

    Alpha Five Version (Registered): 8
    Build: 1874
    Addins: 3133

    Operating System: Microsoft Windows XP Professional Service Pack 2

    Bug Description:

    I created this in A5 V7. I used some code from Dr Wayne�s web site and see that it is in the A5 help files also, to number records in a child table, and then when creating a new record at the parent level the new child table would start numbering with number 1. This works fine in Ver 7 and have created over a 1000 records with no problem. I upgraded to Ver 8 Enterprise Edition and now this doesn�t work.

    Open Test db

    Open �Labor Form�

    Enter Date , Worker, TimeIn TimeOut, Task. These are not significant, or related to the problem.

    The problem is in the embedded browse that has the columns �Line_no� and �Qty�

    In the �Qty� column I start entering 2 digit numbers. I have an attachment �example.pdf� (this is in the "test.zip" file)that shows that data that I am entering.Or, just enter numbers starting with 1, 2 ,3 , etc...

    I enter the numbers like you would a calculator. After entering the data I go to the column �Qty2� and re-enter the data.

    Then in the �Line_no� and �Check� columns will show if I made any mistakes.

    The problem is when entering the data, after several records, I will enter the 2 digit numbers, hit enter and no record is entered.

    On the example.tiff file you will see each column has 47 lines per column. When I get to line 47 of the first column of my example sheet, A5 screen is on maybe line 30.

    The db I have attached has all records removed and it does this in the test.zip

    Once while I was entering data, I got an error message, I don�t remember exact wording and I restored my backup and don�t get the error anymore but it said something like �Cannot resynch on index� I had entered about 50 lines and A5 locked up and all I could get was this message.



    Thank you,

    David L. Aery
    David
    A5V12.3
    Win7, 64 bit
    Qbks 2018 Enterprise
    QODBC R/W
    Tags: None
    #2
    Re: Program runs in Ver 7 but not Ver 8

    David,
    I found that if you turn off referential integrity in your set structure, the browse entry works as it should. Please try it and see if you agree.
    - Peter

    Comment

      #3
      Re: Program runs in Ver 7 but not Ver 8

      David,
      Ignore my last comment -- it's false. Turning off referential integrity doesn't fix it.
      - Peter

      Comment

        #4
        Re: Program runs in Ver 7 but not Ver 8

        David,
        I don't see the problem, though, when I use the default form for the set and make entries there. Can you start from the default form and make modifications one at a time until you see where the problem arises?
        - Peter

        Comment

          #5
          Re: Program runs in Ver 7 but not Ver 8

          David, do you see the problem entering data using the "default form" for the set? I tried to trigger the fault there by entering records into the Qty table browse as fast as I could and I cannot trigger the fault you describe.

          In your custom form you have 3 browse objects all based on the same Qty table. Is there some reason you chose not to use a single browse object? I'm guessing that the data entry issue you're seeing results from the extra work the form has to do to keep all three browses synchronized. Why not use only a single browse object?

          Comment

            #6
            Re: Program runs in Ver 7 but not Ver 8

            In your custom form you have 3 browse objects all based on the same Qty table. Is there some reason you chose not to use a single browse object? I'm guessing that the data entry issue you're seeing results from the extra work the form has to do to keep all three browses synchronized. Why not use only a single browse object?
            Thanks Tom,

            In the default browse there are 3 columns, so you have to hit enter or tab 3 times to go to the next record. The reason for the seperate browses is for speed. I originally had this set up in Excel and there you could move to the cell below instead of to the right.
            This works fine in Ver 7. I wanted to put this on another computer with the runtime, I only have the runtime version for version 8.

            David,
            I don't see the problem, though, when I use the default form for the set and make entries there. Can you start from the default form and make modifications one at a time until you see where the problem arises?
            - Peter
            Thanks Peter.
            I will try that.
            David
            A5V12.3
            Win7, 64 bit
            Qbks 2018 Enterprise
            QODBC R/W

            Comment

              #7
              Re: Program runs in Ver 7 but not Ver 8

              In the default browse there are 3 columns, so you have to hit enter or tab 3 times to go to the next record. The reason for the seperate browses is for speed.
              I don't understand. When you drop the first browse object into your layout you can delete columns you don't want to appear. What purpose do the 2nd and 3rd browses of your Qty table serve?

              Comment

                #8
                Re: Program runs in Ver 7 but not Ver 8

                I don't understand. When you drop the first browse object into your layout you can delete columns you don't want to appear. What purpose do the 2nd and 3rd browses of your Qty table serve?
                I enter records in 1st browse, "qty" field. I use the 2nd browse, "qty2" field, to enter records again to double check my entries. The 3rd browse checks to see if they match, "qty-qty2". then if there is a difference, I go to that record, check the line number on my paper to see what the correct number is.
                David
                A5V12.3
                Win7, 64 bit
                Qbks 2018 Enterprise
                QODBC R/W

                Comment

                  #9
                  Re: Program runs in Ver 7 but not Ver 8

                  David, that's interesting. Are you aware that the validation field rules include the option to require double entry, rejecting a field value if the second entry doesn't match the first? Using double entry mode the user must key the same value twice in order for it to be accepted.

                  Comment

                    #10
                    Re: Program runs in Ver 7 but not Ver 8

                    Originally posted by Tom Cone Jr View Post
                    David, that's interesting. Are you aware that the validation field rules include the option to require double entry, rejecting a field value if the second entry doesn't match the first? Using double entry mode the user must key the same value twice in order for it to be accepted.
                    Thanks Tom, I can see how this would work but, I would like to get this to work in Version 8 if possible. I think the way we have been doing it is a lot faster, but I will check that out.
                    Thanks,
                    David
                    A5V12.3
                    Win7, 64 bit
                    Qbks 2018 Enterprise
                    QODBC R/W

                    Comment

                      #11
                      Re: Program runs in Ver 7 but not Ver 8

                      Ver 10 corrected this problem. Ver 8 or ver 9 it would never work.
                      David
                      A5V12.3
                      Win7, 64 bit
                      Qbks 2018 Enterprise
                      QODBC R/W

                      Comment

                      Previous template Next
                      Working...
                      X