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

Form Resynch OnActivate?

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

    Form Resynch OnActivate?

    Has anybody else seen this issue...

    A customer with about 5 computers on a peer-to-peer network is having an occasional problem during data entry.

    Background:
    I have a customer form used for initial lookup and a second form which has customer order info based on a set. They are separated because (1) the customer lookup can be very complex (trust me) and (2) there are other forms that may be opened once the correct customer is found. In this situation, once they find the customer they then switch to the order form which is based on a set. The set is basically:
    Customer ==> OrderHeader ==> OrderItems

    Situation:
    One person is editing the order which is on the separate form based on a set.
    The second person enters and saves a new customer.
    The first person returns to the customer form.

    Problem:
    The first person now sees (sometimes) the new entry created by the second person??? (I love trouble shooting 'sometimes'!)

    I tried to repeat this on my home computer using the runtime so I could have multiple copies running at once. It was not successful; I can't duplicate the problem.

    The only thing I can see that make me suspicious is that the original customer form has a "this.resynch()" in the OnActivate script. I need something here to update the form because some of the fields in the customer table can be updated when entering orders and I want the changes to show up when the user returns to the customer form. I have replaced the resynch() command with a "sys_send_keys( "{F5}" )" but have no way to tell if this will help since I can't duplicate the initial problem.

    Has anyone else encountered something like this? If so, how did you solve it?
    Tags: None
    #2
    RE: Form Resynch OnActivate?

    Cal, I haven't run into the problem you are describing. It sounds like the record pointer in the customer table is moving 'sometimes'.

    If you always want the user to return to the customer for whom an order was just entered, you could set a flag as the order entry begins, and on return to the customer form if the flag has been set, fetch to the desired customer, and then lower the flag.

    -- tom

    Comment

      #3
      RE: Form Resynch OnActivate?

      The way in which I could see it happening is if *both* data
      entry personnel were entering new customers. Then, assuming
      you use an autoincrement field to identify the customer
      uniquely, it could happen that when clerk 1 moves off her
      customer to create an order, the autoincrement number is
      assigned to the second customer. There is no guarantee
      that autoincrement numbers are going to be the ones they
      appear to be until the record is saved.
      Is the first form also used for adding new customers?

      Comment

        #4
        RE: Form Resynch OnActivate?

        Cal, Speak of the devil, we just went 15 rounds with a very similar problem in our Repair Order that queries our customer table to see if the customer exists and if not allows the user to add the new customer on the fly by automatically taking them to the customer entry form. 'Sometimes' when they returned, a freshly entered customer entered by another client on the network would be displayed on the first persons Repair Order. If this sounds like the same or similar problem here is what we did to correct it. First, our original operation used to leave the current Repair Order being created open while the customer entry form, if needed opened over it. If a new customer was added on the fly, the customer form would simply be closed after the new customer entry and the Repair Order would now be visible again. Much to our surprise, once in while on a network, a customer being entered on another system on the network would now be in the Repair Order? We did two things. One, we now open the new customer entry form, and then save and close the Repair Order before the new customer is entered. The script that closed the Repair Order also gathers any information needed to reopen the same Repair Order number after the new customer has been entered. To the user�s eye, nothing has changed in the operation. By closing and re-opening the Repair Order all the new customer data always displayed correctly and it seems as though the record is taken off the firing line so it is not a target for stray bullets! Second, we added what we call an edit check field and a global check variable. When the Repair Order was closed to enter a new customer on the fly, the check field value is set to 1 and the check variable is set to that clients computer name so that during the new customer entry only that system could regain control of that Repair Order by using both values in a restricted edit environment. This would prevent anyone else on the network from being able to edit the Repair Order until the first person had finished with it and reset the check field to 0 and the check variable to ��. If you�re leaving your forms open, you might want to try closing the forms behind you. All of our problems went away after we started saving, closing and then re-opening the same Repair Order. Before this we had tried about a thousand different fixes with none correcting the problem consistently. We never did figure why this happened, only that we now had it fixed!
        Jeff

        Comment

          #5
          RE: Form Resynch OnActivate?

          Thanks guys. I think I'll first try saving a pointer and doing a 'find' operation when I return to the form just to save the time of redrawing the form. If that doesn't work, closing and re-opening the form completely should do the job.

          (By the way, Peter, thanks for your suggestion because this is something I considered during development but then forgot to implement - more work ahead! However, I did confirm that auto-increment is not the problem in this particular issue since it has happened with customer data that was set up 3 years ago in A4 prior to my conversion to A5.)

          Comment

            #6
            RE: Form Resynch OnActivate?

            Cal, I would be grateful to know if you do find a solution outside of closing and opening the form. This method was not my first choice, just the only thing I could use reliably.
            Jeff

            Comment

              #7
              RE: Form Resynch OnActivate?

              Will do. In fact, I had intended to say in my last note that I would post my results when done.

              Comment

                #8
                RE: Form Resynch OnActivate?

                Cal,
                You didn't mention what version of A5 you're running??? There was a bug fixed some time ago regarding the Resynch problem. A form resynch should NEVER be issued while the table is in anything other than "View" mode. It will corrupt the current pointer. Later versions disabled this feature when in "Enter" or "Change" mode.

                Comment

                  #9
                  RE: Form Resynch OnActivate?

                  Thanks for the suggestion. The 'parent' form is in the View mode when resynching. And, I'm using the latest version.

                  (Although I have A4v2, A4v3, A4v4, A4v6, A5v1.02, A5v3.04, A5v4.03 build 230, A5v4.03 b221, a5v4.5 b263, and A5v4.5 b266 all still installed.)

                  Comment

                  Previous template Next
                  Working...
                  X