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

Refreshing shadow database fails to reflect a change made in the master db

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

    Refreshing shadow database fails to reflect a change made in the master db

    I made a change in the master (server-based) database of my application for tracking IT equipment and work orders. The change was to display
    - only open work orders
    - in descending order on work order number
    in a browse window of the Work Orders form.

    Opening the master database in either the full or the runtime version of A5V9 shows the change was correctly implemented for the master db.

    However, recreating or refreshing the shadow database for any of three distributed applications fails to produce the change in the shadow db. Instead, the work order form of the shadow db
    - displays the work orders in ascending order
    - displays both open and closed work orders

    I have seen the debugger step through the following code of the OnInit event of the shadow db Work Orders form just prior to the producing the above-mentioned results:

    dim tbl as p
    dim indxP as p
    tbl = table.current()
    indxP = tbl.order("invert(WO_Num)", "val(cdate(clsddate))=0")
    topparent.browse1.Refresh()

    Does anyone have an idea about what is going wrong here?
    BTW up to now, I have successfully made changes in the master db that have been properly reflected in the refreshed shadow dbs.

    #2
    Re: Refreshing shadow database fails to reflect a change made in the master db

    Check the workstations for shadow copies of the database in a different directory. Sounds like you've got two installed, you're updating one, but running the other.

    Comment


      #3
      Re: Refreshing shadow database fails to reflect a change made in the master db

      Thanks for the suggestion, Tom. However, I have been using a bootstrap to create a new shadow database and have always chosen the same directory for its location.
      Eileen

      Comment


        #4
        Re: Refreshing shadow database fails to reflect a change made in the master db

        I have no idea as to what may be going wrong. But see what happens if you delete the folder with the shadow and then create it from scratch in the same location (folder). I know in the past (v7 maybe v8) there were some problems with refreshing shadows, but my impression has been that all that is no longer a problem with v9--but maybe not.

        Comment


          #5
          Re: Refreshing shadow database fails to reflect a change made in the master db

          Have you verified that the workstations are correctly pathed by making a new dummy entry with a non-shadowed copy, and then checking a shadowed copy for that record entry?

          Unless I am mistaken, a bootstrapped install gives the user the ability to change the install directory.

          Also, is this your first shadow refresh? Were other refreshes successful?
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            Re: Refreshing shadow database fails to reflect a change made in the master db

            Martin, thanks for the suggestion to verify the path. I entered a new work order into the master db and the entry is present via the shadow db.

            I twice made minor changes to the master db application and then successfully distributed the changes to user PCs by
            - deleting directory of the shadow db
            - recreating the shadow db from the bootstrap application
            In this process, I always have used the same path for the shadow db directory.

            It was only on this third change to the master db, that the newly constructed shadow db failed to reflect the change. Then I decided to open the app of the shadow db and refresh the shadow. The refresh did not correct the problem.

            Comment


              #7
              Re: Refreshing shadow database fails to reflect a change made in the master db

              well phooie!!!!
              something is rotten in Denmark, what what!!

              try this:
              uising the full version of Alpha,
              open the master db on the server
              go to the control panel
              tools
              network optimization
              options
              increment the number by one
              set it to auto refresh the db
              save it and then open the shadow copy on the workstation
              it should auto refresh the workstation
              see if that fixes it
              Cole Custom Programming - Terrell, Texas
              972 524 8714
              [email protected]

              ____________________
              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

              Comment


                #8
                Re: Refreshing shadow database fails to reflect a change made in the master db

                Another idea that might provide additional clues:

                On the troubled workstation start Alpha Five from the START menu, not from your shortcut.

                This will open Alpha without opening a database.

                Use the File Menu at top of screen to "open a database" and browse over to the server to open the live database there manually. Then use the tools menu option to network optimize the local workstation manually. Tell us whether your changes "stick" when you then open the shadow copy of the database you just created. Tell us whether your newly created shadow copy is in the same folder as the shadow copy created by your bootstrap app.

                Possible explanations:

                a) something in your bootstrap app is failing on the one troubled workstation - perhaps because of a permissions issue

                b) you have two copies of the database on the development machine and you're updating one, but running the bootstrap app against the other...

                c) your workstation has two copies of the shadowed database... your shortcut is opening the copy that's not being refreshed (or rebuilt) by your bootstrap app

                Comment


                  #9
                  Re: Refreshing shadow database fails to reflect a change made in the master db

                  Thanks again for your suggestions, Martin. They truly seemed hopeful. However, I'm beginning to share your sentiments of PHOOIE!
                  I stepped through the network optimization from the master db. Instead of Save, the V9 Platinum option is "Create Shadow Database" where it creates the database \my documents\shadow\trackit\trackit.adb. When all this was accomplished and I opened the new shadow db in its new location, the changes failed once again to materialize. :>((

                  BTW I have submitted this to alphasoftware for product support. I'm thinking it might be a bug but I should get a quicker response from product support.

                  Comment


                    #10
                    Re: Refreshing shadow database fails to reflect a change made in the master db

                    if you have or get the free version of logmein, you could call and then send an invitation to me or Tom to come on and see if we could help you out.

                    You would need to send the invitation from a computer that would let us have access to the program and the server - with a full (not runtime) version of the Alpha software.

                    my number is 972 524 8714
                    Cole Custom Programming - Terrell, Texas
                    972 524 8714
                    [email protected]

                    ____________________
                    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                    Comment


                      #11
                      Re: Refreshing shadow database fails to reflect a change made in the master db

                      eileen,

                      please, where is the desktop icon properties pathed to. It sounds to me like you are running the app in a different folder than where your new shadow is located.

                      I believe(may be wrong) that most of us have our shadows running on the c: root path like " c:\myapp " Alpha for some reason always wants to add a folder underneath like " c:\myapp\shadow ".

                      If your shadow goes to a certain folder, then the icon on the desktop has to go to wherever you sent the shadow.

                      actual path in icon "C:\ups55v9\sales.adb" for my app - "c:\ups55v9" is where the shadow is
                      Last edited by DaveM; 07-29-2009, 03:16 PM.
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment

                      Working...
                      X