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



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

Tracking individual records as unsynced

  • Filter
  • Time
  • Show
Clear All
new posts

  • Tracking individual records as unsynced

    I am trying to figure out how to track a specific record as unsynced. I am conditionally styling each row in the list control as tan (unsynced) or green (synced). The problem I am running into is that often when syncing in large batches (200-400 records) the user may lose connection to the server resulting in only half of the records successfully being synced. I have tried to find an e.<something???> object in the onItemDraw event or on the detail view events I tried to find something similar, but nothing turned up. I also tried to find any alpha method or object that tracks the row numbers of dirty records which would be supremely helpful in this case. If anyone has any ideas I would greatly appreciate them! Thanks!

  • #2
    Re: Tracking individual records as unsynced

    If I'm understanding the problem correctly (ie. the client app doesn't always get notification that all records were synched), I believe Alpha added the Server-side synchronization log table feature to address it.

    You can check the option for the list in the list properties' "Detail View" tab.
    But you also have to configure the synch table in the Web Project's 'Project Properites' window (down in the "Offline Data Synchronization Log Table Settings")


    • #3
      Re: Tracking individual records as unsynced

      Well the real problem is that I am syncing in batches and if I were to lose connection (or walk out of coverage), my list control would only be partially synced. So I need to find some way to quantitatively track which records are dirty, or synced. I can just use the css styling for records in the list control, but I also need a dynamic image to change showing that I have successfully synced that record.

      I am looking into the on afterSynchronizeRecord event in the detail view pane because I think if I could send the row index of synced records to a javascript array. I pretty much never use Xbasic and so I was just wondering how to send information from xBasic to JavaScript. The event prototype says: "Your code can optionally send back Javascript by setting the e.javascript property."


      • #4
        Re: Tracking individual records as unsynced

        But again I believe that the "Offline Data Synchronization Log Table" feature was developed by Alpha to help us address these types of sync problems.
        The page explains more:

        There is some extra work needed to put it all together. Yes, the server will have the synchronization log and will know what data it succeeded in integrating in the back-end. On the other side, the client app will know, assuming that everything was put together "correctly", the number of records "to be synced" doesn't match the response - or lack of response - from the server confirming the number of records synced.
        When this quantity difference is detected and depending on the nature of the data to be synced, you have a choice to either try to re-sync the records (but not in the case where your database/client-side list control configuration is set up to allow the database to assign an auto-incremented primary key), simply call for a refresh of the data from the server, or some other specific solution that would be best for your specific case. I imagine it would be too hard for Alpha to create a "one solution fits all" for resolving various sync/connectivity issues.

        In fact, all the sync features is one of the main reasons that I appreciate using Alpha. "Only" a few thousand US$ to have 99% of a fairly solid sync system written for me.


        • #5
          Re: Tracking individual records as unsynced

          This is super helpful thanks!


          • #6
            Re: Tracking individual records as unsynced

            I got this working and this is perfect for what I'm trying to do!