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

Trying to populate sys_shell() with variables

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

    Trying to populate sys_shell() with variables

    I have been trying to use variables with sys_shell() but I am not having any luck.

    Basically I need to have a button open another Alpha5 workspace using command line options like I would with a desktop shortcut.

    If I hard code the argument in sys_shell() it works just fine.

    If I use variables to build the command line with options it will open Alpha5 but will not start the workspace.
    The strange thing is I can copy the results of the variable " ?opentr " and paste it into sys_shell() and it will work.

    So even though for example sys_shell(opentr,1) has the exact same contents of sys_shell("C:\Program Files (x86)\a5V11\Alpha5.exe ""c:\tr\tr2.adb"" -INCLUDE=""c:\tr\TR.startup""",1) which will work.

    Why do I need to do this with variables instead of just hard coding? Because not all my customers install my main app on C:

    I have attached a sample db if any care to help me figure this out. Just unzip it in an empty folder and then open the tr.adb file with Alpha5

    Thanks in advance for any help.
    Attached Files

    #2
    Re: Trying to populate sys_shell() with variables

    i did not download your database but thinking it aloud
    how about trying with filename decode to send the path of database installation, and use filename_encode to encode the location earlier on?
    according to the description this makes it less location dependent.
    or use
    sys_shell(evaluate_string(opentr),1)

    i don't have desktop experience, so this could be naive attempt.
    thanks for reading

    gandhi

    version 11 3381 - 4096
    mysql backend
    http://www.alphawebprogramming.blogspot.com
    [email protected]
    Skype:[email protected]
    1 914 924 5171

    Comment


      #3
      Re: Trying to populate sys_shell() with variables

      Try

      Code:
      rtpath = A5.GET_EXE_PATH()+ "\\"+"Alpha5.exe "
      dbpath = quote(A5.GET_PATH()+ "\\"+"tr2.adb")
      wspath = A5.Get_Path()+"\\"
      incl =  "-INCLUDE=\""+wspath+"TR.startup\""
      opentr = rtpath+dbpath+incl
      sys_shell(opentr,1)
      There can be only one.

      Comment


        #4
        Re: Trying to populate sys_shell() with variables

        Thanks to both of you.

        Stan. The code you posted worked. I had tried adjusting the quote marks and even using the quote() function but I guess I never hit on the right combination myself. I guess because I was focused on the results of ?opentr needing to look just like I had the hardcode.

        Again, thanks to both of you. I really appreciate it.

        Comment


          #5
          Re: Trying to populate sys_shell() with variables

          My process was similar but I worked back from the end result.

          I captured the Target line from an existing shortcut, quoted the overall target line and escaped internal quotes.

          Then I tortured the individual parts until I had something I could concatenate to yield the target line in the interactive window.

          Code:
          Original target line
          C:\Alpha\a5V11\alpha5.exe "P:\revionics\datastor.adb" -INCLUDE="P:\revionics\datastor_Revionics.startup"
          
          Quoted and escaped target line
          "C:\Alpha\a5V11\alpha5.exe \"P:\revionics\datastor.adb\" -INCLUDE=\"P:\revionics\datastor_Revionics.startup\""
          
          'output in interactive window
          ? "C:\Alpha\a5V11\alpha5.exe \"P:\revionics\datastor.adb\" -INCLUDE=\"P:\revionics\datastor_Revionics.startup\""
          = C:\Alpha\a5V11\alpha5.exe "P:\revionics\datastor.adb" -INCLUDE="P:\revionics\datastor_Revionics.startup"
          There can be only one.

          Comment


            #6
            Re: Trying to populate sys_shell() with variables

            Originally posted by preston2 View Post
            Thanks to both of you.

            I had tried adjusting the quote marks and even using the quote() function but I guess I never hit on the right combination myself. I guess because I was focused on the results of ?opentr needing to look just like I had the hardcode.

            Again, thanks to both of you. I really appreciate it.
            i think the space between the command is the problem
            if you declare
            dim cs as c
            cs = space(1)+"c:\tr\tr2.adb"
            then sys_shell("C:\Program Files (x86)\a5V11\Alpha5.exe " + cs,1) will open the correct adb
            then you need to pass the include, i haven't tested that yet.(because i do not know to work in desktop )
            thanks for reading

            gandhi

            version 11 3381 - 4096
            mysql backend
            http://www.alphawebprogramming.blogspot.com
            [email protected]
            Skype:[email protected]
            1 914 924 5171

            Comment

            Working...
            X