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

Index updating while shared

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #16
    Re: Index updating while shared

    Hi John,

    Originally posted by johngtatp View Post
    The code is a calculated field on a form,
    The formula is:
    numrentcars = dbcount("rcardetail","resnum_type",*concat_keys(resnum,type))
    The resnum_type index has an order expression of *CONCAT_KEYS(RESNUM,TYPE) with no filter

    The numrentcars is displayed in a embedded browse

    All users have this form open and have the network refresh set every 15 seconds. When one user saves a record which should update the count, the other machines sometimes reflect the change and sometimes do not. If you restart alpha (not just close and open the form) the correct count is always displayed. I have also tried using a button that has an action script to refresh the display which in xbasic is:
    topparent.Commit()
    topparent.Resynch()
    topparent.Refresh_Layout()
    but that does not refresh the count when it is incorrect. I hope that makes sense.
    The DBCOUNT and it's usage looks correct. *CONCAT_KEYS() is a newer function that I don't think you need here, and while it looks correct, I'd try a simpler resnum+type expressions in place of it and the index order expression to eliminate that as a possible problem.

    The Calculated field will not automatically update unless resnum or type in the parent table change while in change mode, or when saving a record. In view mode it will probably never change except upon fetch of a new parent record, or possibly when a network refresh occurs (By the way, a network refresh eats up a lot of network bandwidth if you have many users and only happens during view mode. Not recommended)

    Rather than using numrentcars on the embedded browse, try placing it as a form field instead. This may have something to do with it.

    You may also still have to refresh the field manually to have it update while not doing anything, but I'd do it just to that field, not the whole form (It would have to effectively force a recalc of calc fields.)

    Another way would to get this value which may be beyond your current abilities is to recalculate the value on events like onfetch and onsave to a variable and display the variable on the form.
    Regards,

    Ira J. Perlow
    Computer Systems Design


    CSDA A5 Products
    New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
    CSDA Barcode Functions
    CSDA Code Utility
    CSDA Screen Capture

    Comment

      #17
      Re: Index updating while shared

      Another way would to get this value which may be beyond your current abilities is to recalculate the value on events like onfetch and onsave to a variable and display the variable on the form.
      I think this is especially promising. If you didn't mind spending the processing time, or the increased network traffice this would cause, you could put such a script in the onTimer event for the form.

      Comment

        #18
        Re: Index updating while shared

        Update: There is an issue when using indexes in a multi user enviornment. In my case both users are on the same form and have cached the index if another user makes a change that say a calculated field needs to use, i.e. dbcount in my case, the first user will not see the change until they themselves make a change which requires the index to be re-read. A new function has been added which I am about to try and here is the verbiage from the pre-release

        <table>.flush_indexes() Method - Causes Alpha Five to reload index key values.

        This method would only be needed in the following condition:
        1.Two or more Alpha Five instances are running (e.g. user1, user2)
        2.Both users have a form based on the same table open.
        3.User2 makes a change that causes an index update.
        4.User1 executes some Xbasic (such as a db_count(), or lookupc()) which relies on an index. Since user1 has cached the index keys, he will not see user2's changes unless he first re-reads the index.

        Comment

          #19
          Re: Index updating while shared

          Ok, another suggestion John.
          Would it be possible to use the POST feature to maintain a running total?
          Then a simple RefreshObject would display the current information.
          See our Hybrid Option here;
          https://hybridapps.example-software.com/

          Apologies to anyone I haven't managed to upset yet.
          You are held in a queue and I will get to you soon.

          Comment

            #20
            Re: Index updating while shared

            Originally posted by johngtatp View Post
            Update: There is an issue when using indexes in a multi user enviornment. In my case both users are on the same form and have cached the index if another user makes a change that say a calculated field needs to use, i.e. dbcount in my case, the first user will not see the change until they themselves make a change which requires the index to be re-read. A new function has been added which I am about to try and here is the verbiage from the pre-release
            Where did you hear about this "flush_indexes" method? Is it something you created? I tried it in A5v9, v10, and v11 and got "property not found" every time.

            Comment

              #21
              Re: Index updating while shared

              Originally posted by CALocklin View Post
              Where did you hear about this "flush_indexes" method? Is it something you created? I tried it in A5v9, v10, and v11 and got "property not found" every time.
              http://downloads.alphasoftware.com/A...easenotes.html

              use the browser find
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.
              "Make it as simple as possible, but not simpler."
              Albert Einstein

              http://www.iadn.com/images/media/iadn_member.png

              Comment

                #22
                Re: Index updating while shared

                Ahh! I missed the "pre-release" comment. I guess that explains why it's not recognized in my current version. Thanks.

                Comment

                Previous 1 2 template Next
                Working...
                X