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

Tabbed Object Problem

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

    Tabbed Object Problem

    I have a problem with Tab objects on at least two forms in my application.

    The forms relate to sets of data. Different parts of the data set are placed on different tabs. The application has been configured that way for many years and has always worked flawlessly until upgrading recently to A5V5.

    If I start the form, then attempt to change a value on the first tab, I will get the error message:

    "Field required:Name".

    See attached Word document below for reference.

    If I first switch to another tab before I start to edit a value ("Vendor" browse in Parts, "Where Used" browse in Machines), then immediately switch back to the main tab, everytying works just fine.

    From this I conclude that the data is not corrupted and the application is programmed correctly. Being able to "make it work" by switching initially to another tab makes me wonder if this is a bug in A5V5. I am running on Patch 1408-1035. Can you either:

    * Confirm that this is a bug and solve it, or
    * Let me know of a way to initialize the form in such a
    way as switching to tabs before editing.

    Thanks

    Andy

    #2
    RE: Tabbed Object Problem

    Andy,

    1. Delete the field from the form;
    2. Save the form;
    3. Using the drag drop list, drag and drop the field onto the form.

    Often times, during conversion, things can get slightly messed up. I had a similar problem and did the above. All is well.

    kenn
    TYVM :) kenn

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

    Comment


      #3
      RE: Tabbed Object Problem

      I take it that name is designated a required field in field rules.

      If so, then there is an interaction between the order in which you activate the fields on your form and the field rule requirement.

      The first thing to do in such situations is always to see if the default form generates the error. If not, then look at the way you have set up things in your tabbed form to produce the error.

      In design mode, set the tab order (arrange/set tab order) so the name field is reached in the appropriate point in the data entry sequence.

      This is not a bug in A5.

      Bill
      Bill Hanigsberg

      Comment


        #4
        RE: Tabbed Object Problem

        Hi Andy

        Take a look at Msg ID: 24423

        This solution workes for me and it has worked for few others

        Regards
        Robert

        Comment


          #5
          RE: Tabbed Object Problem

          Robert,

          thanks for your suggestion. The solutin from Msg 24423 worked for me as well.

          I hope that Alpha Software will solve this bug at some point, but for now I am ok.

          Thanks

          Andy Sigrist

          Comment


            #6
            RE: Tabbed Object Problem

            Robert,

            what's the quick way to find message thread 24423 ?

            When I search for 24423 I get zero hits.

            -- tom

            Comment


              #7
              RE: Tabbed Object Problem

              I searched for Msg ID: 24423 and 24423. The first yielded 1 hit and the latter 3 hits, all of which are responses to this thread.

              Then I searched using the same parameters using quotes. Same 4 hits.

              I concur with Tom, whta's the secret?

              kenn
              TYVM :) kenn

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

              Comment


                #8
                RE: Tabbed Object Problem

                Hello Tom

                I have found a solution to the problem that works for me.

                I am not sure that it may solve the problem for everyone but I think it may.

                The problem is, as far as I have found, "Required Fields" and "Custom Validations".

                If you don�t need them in the field rules, just eliminate them and the problem should be gone.

                However if you need them, and I suspect you do, then I have found another solution. I also suggest that you make backups of everything before you implement my suggestion and then test everything before you start using it.

                I have found that the problem is not the tabbed forms. The problem is with the embedded browses, for you will get the same problem with browses in conditional objects or if the browse is hidden. In other words Alpha5v5 needs to see the browse at all times and it also needs to refresh it constantly.

                The solution is to create two of each embedded browses. One you place wherever you need to, the second or as I call it (the dummy browse) you place it where it is always visible.

                To solve the space and other problems, I set the dummy browse to disable and read-only in the property section.

                I then uncheck all the dummy browse "Apperance" properties except for the "parent record only" property, for I will not be using this browse. Then, not to make it an eye sore, I set everything on the browse to the same color as the form background, make all columns and rows as small as possible, so not to take much room on the form, and place it wherever you have room on the form. Remember these dummy browses must be always visible and on top.

                Another must, all fields that are "Required", and have "Custom Validations" must be in the dummy browse, no need to put other fields in it.

                I then go to the "OnTimer" event for the form ( I have it set to 1/2 second) and I create a script that 'Refreshes" all the dummy browses.

                You could place a script like this one in the INLINE XBASIC

                'Refresh dummy browses in the current form.
                topparent:Browse_dummy1.refresh()
                topparent:Browse_dummy2.refresh()
                topparent:Brows_dummy3.refresh()

                This will insure that the browses are constantly refreshed.

                I have also found another problem. If you go to the browse from a field which is one of the parent linking fields in the set, you will get the error also, so make sure that this filed is either set to disable or on the "OnDepart" event make it go to another field and then in the browse.

                Robert

                Comment

                Working...
                X