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

appversion reset auto

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

    appversion reset auto

    All Help appreciated

    application is in production now.
    app version is set
    app uses alpha security with more than a few users
    app uses shadowing - set to force re-shadow when appversion changes upward
    user never sees anything but the screens they need.

    How can I cause the app version to change at the server level in the application without over writing the adb files?

    I can get the new app number there easy enough, but the shadow will not allow a appversion change(would make it easy). I have one overwritten table with an update. I can place the new app version in there. I can use it to update. I just can't figure how to do it from the shadow. Maybe I am getting dense?

    Any ideas would be helpful.
    Last edited by DaveM; 03-18-2016, 11:44 AM.
    Dave Mason
    [email protected]
    Skype is dave.mason46

    #2
    Re: appversio reset auto

    I thought a command line would work, but no.
    I tried this with the tested code in a script

    C:\alda12\alpha5.exe "c:\wswp\myapp.adb" -hide -nosplash -executeandexit -command=scriptplay("setver")
    It opens the app, but does not execute the script then asks for a user name and password, and closes - never runs the script

    another try
    C:\alda12\alpha5.exe "c:\wswp\batchcommand" -hide -nosplash -executeandexit -command=scriptplay("setver")

    You would swear this one worked, but no. Version remains the same.

    Script is:
    Code:
    dim t as P
    t = table.open("c:\winswap\aaap.dbf",FILE_RW_SHARED)
    query.filter = "recno()="+1
    query.order=""
    query.options = "T"
    qry = t.query_create
    x = t.version   ' new one is 16.0321 and old one is 16.0319
    y = A5_GetAppVersionNumber()
    if x<>y then
    A5_SetAppVersionNumber(x)
    end if
    Trialed in editor, this works fine every time.
    Last edited by DaveM; 03-18-2016, 12:13 AM.
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment


      #3
      Re: appversion reset auto

      Hi Dave,
      Check out this function in the Code Archive
      I call it from the AutoExec: ShBldMgmt()

      Robin

      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

      Comment


        #4
        Re: appversion reset auto

        Thanks Robin

        I already use that

        The issue is that when I send them a new adb with the new version number, it overwrites their users.

        The Idea is that I can send an update to their app that does NOT overwrite the adb and then on shadowed app start, update the adb version number. Once the version number is updated, shadow update happens on next start.


        The problem is, I can't seem to get the version number to change except manually or by running the master directly as administrator. I can do that fine, but the clients cannot and I do not want them to. That would be a security breach possibility.
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment


          #5
          Re: appversion reset auto

          I tried to do that too, but you can't from the shadow only from the developer.
          Robin

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

          Comment


            #6
            Re: appversion reset auto

            Tom Cone gave me another idea.
            Bypass it altogether.
            I am sending a small encrypted table with old and new version numbers with the update. If they do not match, reshadow. and I can do that from the shadow.
            It will completely by-pass the version control in the adb files.
            But, you do what you have to do.
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment


              #7
              Re: appversion reset auto

              I got help from Tom cone for this idea.
              I have 2 tables, one never gets overwritten with an update the other always does, so I can place the newest version number in the replaced table and checked against the old version number and shadow refreshed as needed. This only works from the shadow.

              Hope it helps someone else!

              Code:
              ' check for shadow
              dim this_path as C
              dim bare_path as C
              dim app_path as C
              dim shadowed as L
              this_path=:a5.Get_Path()
              bare_path=:a5.Get_Master_Path()
              if len(alltrim(bare_path) ) = 0 then 'if zero, not shadowed
                  shadowed =.F.
                  goto theend   'if not shadow - goes to the end of script
              else
                  shadowed =.T.
              end if
              
              dim t as P
              t = table.open("c:\wswp\aaap.dbf",FILE_RW_SHARED)   'holds the new version number
              query.filter = "recno()="+1
              query.order=""
              query.options = "T"
              qry = t.query_create
              newver = t.version
              
              dim tbl as p
              tbl = table.open("p32",FILE_RW_EXCLUSIVE)  'holds the current version number
              query.filter = "recno()="+1
              query.order=""
              query.options = "T"
              qry = tbl.query_create
              oldver = tbl.curver
              
              dim reset as L
              if oldver <> newver then
              reset = .t.
              tbl.change_begin()
              tbl.curver = t.version
              tbl.change_end()
              else 
              reset = .f.
              end if
              t.close()
              tbl.close()
              
              If reset = .t. then
              	REFRESH_SHADOW()
              end if
              theend:
              Dave Mason
              [email protected]
              Skype is dave.mason46

              Comment


                #8
                Re: appversion reset auto

                After all of this, I changed methods completely. Mainly, not wishing to get into the users names and passwords issues.

                All of the adb part will not change and thus, did the code to aex file. The aex can be installed separately.

                The version is kept in a file that always goes with and update and it has a logical code for the update.

                On start of the shadow after an update that is only done to the "server" files, the logical is change and the shadow is refreshed.

                Much simpler and easier to maintain.
                Dave Mason
                [email protected]
                Skype is dave.mason46

                Comment

                Working...
                X