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

Refresh Shadow... in Autoexec

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

    Refresh Shadow... in Autoexec

    We have refresh shadow in the autoexec but it does not seem to refresh everything. For example, I added a button to a form which opened/printed a report... using my development workstation, going directly against the server's database.

    Then, from a workstation loaded with the runengine and a shadow... I opened the database and the refresh shadow in the autoexec seemed to run. The new button was on the form... where I put it... but when clicked, I received a message that the report was not found. I ran refresh shadow again (we have a button for the user's to do that without having to get and out of the database) and then the button/report worked fine.

    What am I missing?

    Thanks
    "all things should be as simple as possible... but no simpler"

    Mike

    #2
    Re: Refresh Shadow... in Autoexec

    I seem to have a fuzzy recollection that people were complaining of problems w. refresh_shadow(). But don't quote me. I know I did in ver. 5, so I wrote my own comprehensive function to do that. I really don't know what has been fixed or not, but take a look at: create_shadow() and create_shadow2().
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: Refresh Shadow... in Autoexec

      Thanks Peter... we will take a look... re-creating the shadow, rather than updating it... hmmm... whatever works.

      Not a big deal, but we hate "little things" that cause end-users to "scratch their heads" and ask questions like "what's up with that, that doesn't make any sense..." We hate anything, real or imagined, that causes users to doubt, lose confidence in, etc. the product.
      "all things should be as simple as possible... but no simpler"

      Mike

      Comment


        #4
        Re: Refresh Shadow... in Autoexec

        Originally posted by michaelwpayton View Post
        ... we hate "little things" that cause end-users to "scratch their heads" and ask questions like "what's up with that, that doesn't make any sense..." We hate anything, real or imagined, that causes users to doubt, lose confidence in, etc. the product.
        Agreed.
        Peter
        AlphaBase Solutions, LLC

        [email protected]
        https://www.alphabasesolutions.com


        Comment


          #5
          Re: Refresh Shadow... in Autoexec

          [sorry... posted as a reply, instead of a new post]

          OK guys, here's an ugly one.

          I 'believe' we are close to coming to the conclusion that backing-up a database, with the "compact option" selected, is trashing at least some number of indexes... depending on some other, unknown at this time, variable relating to, perhaps, files being left open on a MS SBS... even though it seems all users properly shut-down Alpha before the backup runs.

          I know... doesn't make sense... but we have been working on/diagnosing a problem which is easily corrected via "updating all indexes," and we are close to being able to recreate the problem, on demand. That is, we can recreate the problem 7, 8, or so, times out of 10. BUT... we can only recreate the problem with a particular database.

          We know index problems are typically caused by "computing environment issues," i.e. network problems, PC problems, drivers, etc... but this one has us stumped. Any ideas, recollections of anything like this coming up in the past?

          Thanks
          "all things should be as simple as possible... but no simpler"

          Mike

          Comment


            #6
            Re: Refresh Shadow... in Autoexec

            Back to question #1:

            Why would you run a refresh shadow in your autoexec? I can't see any reason for doing that. That seems like it would create an endless loop. Obviously it doesn't since you are doing it but I thought the autoexec ran again after refreshing the network optimize - which would start another optimize which would start another - oh, never mind, you get the idea.

            Why not just set a network optimize number and let A5 run the optimize after the number is updated and the workstation restarts A5? That's all I do and I have many apps and many users out there doing it that way with no problems.

            Sorry, no current thoughts on question #2 because I use my own backup routine which doesn't seem to cause these problems.

            Comment


              #7
              Re: Refresh Shadow... in Autoexec

              Originally posted by CALocklin View Post
              Back to question #1:

              Why would you run a refresh shadow in your autoexec? I can't see any reason for doing that.
              We "rolled our own" version control because, for one, the built-in functionality you are referring to does not have any respect for/accomodation for "local work" which may have been done by a network user on their shadowed copy.
              "all things should be as simple as possible... but no simpler"

              Mike

              Comment


                #8
                Re: Refresh Shadow... in Autoexec

                Thanks. That makes sense.

                Comment

                Working...
                X