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

Rename a UDF in the Autoexec - How?

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

    Rename a UDF in the Autoexec - How?

    I am still thinking this thru as to what I might do or can do for this scenario...I have 2 versions of the function that opens my toolbox panel - one of which is designed for the Runtime version and omits the tasks that require Admin level to run. And since the Admin users have the development version I only need to test for a5_is_runtime() in the Autoexec. However, the original function is coded into all the toolbars and several other functions so adding code to change which function gets called would be next to impossible to accomplish.

    Then I had the bright idea that if I could just rename these 2 functions in the Autoexec so when the ActMenu() function is called in the runtime, it really runs the ActMenu1() code but under the original name. Makes sense to me - but how would I do this?
    Robin

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

    #2
    Re: Rename a UDF in the Autoexec - How?

    Well udf_rename() looked promising but not as much as import_scripts_udf() does. All I had to do was edit the original functions adding a comment line to each so I could tell which was which, then back them up and export them - each with a descriptive name. Then I edited the text files so when importing, either one will point to the same udf ActMenu() and overwrite it. Easy - peasy! Now to modify my Autoexec...

    I think that instead of testing for the runtime, I will just test for the logged in user level. That way if an Admin wants to log into another workstation, they can get the full menu panel to use, log out and when the regular user logs back, they will get the modified one. So I can also add this test to my log in script.
    Robin

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

    Comment


      #3
      Re: Rename a UDF in the Autoexec - How?

      Just thinking. If you can test for the logged in user level couldn't you do that in the ActMenu() function (just one) and branch to the appropriate set of code within the function?

      FUNCTION actmenu AS L ( )
      'test user level to useerlevel variable
      if userlevel = "Admin"
      'do admin stuff
      else
      'do user stuff
      end if
      END FUNCTION
      There can be only one.

      Comment


        #4
        Re: Rename a UDF in the Autoexec - How?

        It would mean editing the xml and not just the code section. This toolbox is not using a table to get the xml definition like my other Menu does, so this way seems easier since it has over 2500 lines of code already!
        Robin

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

        Comment


          #5
          Re: Rename a UDF in the Autoexec - How?

          You already have your solution and nothing wrong with it at all but thinking further.

          actmenu() could be as simple as (after renaming the two versions of the original actmenu())

          FUNCTION actmenu AS L ( )
          'test user level to userlevel variable
          if userlevel = "Admin"
          actmenu_admin()
          else
          actmenu_user()
          end if
          END FUNCTION
          There can be only one.

          Comment


            #6
            Re: Rename a UDF in the Autoexec - How?

            That is an interesting idea too and probably easier to implement. Thanks. However, the login script is the trigger so perhaps I could add a flag to the udf and use that to test which one to run.
            Robin

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

            Comment

            Working...
            X