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

settings to runtime shadow

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

    settings to runtime shadow

    Question. I had a situation where I had created a custom menu, and even though I created it in A5V5, the convert dialog came up when it was first used. I answered always convert/don't ask me again - but it did not copy those settings to the runtime shadow on the workstations.

    Now while my current app for the client can be opened on up to maybe 25 terminals, (and, thus you would have to go to 25 terminals, and enter the settings for each one,) we are working on one that will be installed on over 200 terminals, (although it won't be used by more than 25 at a time.) So, going to 200 terminals to enter the settings would be horrendous. Is there a way, especially via xbasic, to copy the settings from the master on the server to all workstations, as when they refresh the shadow?
    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

    #2
    RE: settings to runtime shadow

    Martin,

    Where are the settings being entered?

    I was thinking of all the ways you could do this, and then began to wonder why you wouldn't just have a table in your app to store settings.

    XBasic has file commands....

    I don't think I'm getting the problem.

    ===Blake===

    Comment


      #3
      RE: settings to runtime shadow

      Martin

      The settings related to a database are saved in the database data dictionary, which does update on a refresh. Setings that apply to the program are saved locally in the A5 program files, which do not. Hoever, you should not be getting a convert message if the menu and toolbar were created in A5V5. It is possible the message was for a toolbar created in a previous version.

      Once all of the menus and toolbars are converted to the latest configuration, you should not get that message at all. After a refresh is done on each workstation, none of them should see any issues either, as all menus and toolbars are in the database data dictionary, which is updated on refresh.

      Jerry

      Comment


        #4
        RE: settings to runtime shadow

        Jerry, that's what I thought, too.

        Try this, in settings, use the default options for "old menus" and "old toolsbars" - i.e., prompt=yes. (This is one of the settings that does not get refreshed from the shadow, on mine, anyway.)

        Then make a new blank menu - call it myblankmenu. Then, make two more, called myblankmenu_edit and myblankmenu_view, so you can prevent the user from having a right click menu for fields a given form.

        Then assign the menu myblankmenu for the rightclick menu for a form, and for a field on the form - apply to all fields. (This is the only way I know of to prevent right click menus for a form when in enter/edit mode.)

        Open the form, be sure you are in either enter or edit mode, and right click on one of the fields. See if you get the convert dialog.

        Although I am about 2 months away from needing to do this, I am wondering how I can come up with a routine that would ensure ALL settings for the runtime app are the same for all workstations, without doing it manually. Settings, like "preferences," must apparently be set from the local workstation.

        In theory, there should be a file I could copy from one to all that would catch the settings.

        They currently use Novel on the server where the app would reside, and want to use a Novel "push" to install the apps. So if I manually do the first install, if I were to copy certain files, then the "push" would do the same thing, thus insuring all settings would be the same.
        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


          #5
          RE: settings to runtime shadow

          Martin

          You only get the message if the menu is completely blank, i.e, no code at all. Just add a separator and the message goes away.

          Most of the other settings for the program are saved in the Windows registry settings. For example, the registry values to convert the menus is as follows

          [HKEY_CURRENT_USER\Software\Alpha Software\Alpha Five 5.0\preferences\old_Menu]
          "conversion_preference"="Convert"
          "prompt"="Yes"

          A good rule of thimb is to design your databse to run with the default settings. Then any installation will run the same as the original.

          Jerry

          Comment


            #6
            RE: settings to runtime shadow

            Thanks
            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


              #7
              RE: settings to runtime shadow

              Jerry, although I'm not sure of the syntax, could I just copy the entire "preferences" key. Although I see your point about doing it so that it will work with the defaults.
              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: settings to runtime shadow

                Martin

                You could export the key from the development computer and import in back into another, by why bother. I don't like messing with the registry unless I must. Most of the settings effect development settings, not settings that effect a running program. Unless you have a specific need to set a setting of that type, I would avoid altering a registry key.

                Jerry

                Comment

                Working...
                X