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

sys_open used with ui_get_text

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

    sys_open used with ui_get_text

    Hi,

    I am trying to write a script that would allow a user to enter a file name and open it with a button.

    The following script works correctly
    file="C:test.doc"
    sys_open(file)

    However if I use, to allow the user to enter the file name

    file dim as c
    result dim as c
    file=ui_get_text("get number","enter file number Ex: test.dot")
    result="c:file"
    sys_open(result)

    That does not work, I also tried result="c:+file"
    result="c:+""+file" etc without any success.

    What am I doing wrong, or may be "sys_open" will not work that way.?

    Thanks for your help

    Regards to all

    JP

    #2
    RE: sys_open used with ui_get_text

    Hi Jean
    I got this work but to enter the full path in the dialog box. In my test I entered "C:booth.doc" - trying to parse "c:" with the var didn't work because it doesn't like the backslash char. I didn't find the ascii equivilent or I would have tried that. Just using "C:"+alltrim(resp)would work, but I believe it would only look for the file in the current directory (didn't try it)

    dim global resp as c
    resp=ui_get_text("","File Name")
    resp=alltrim(var->resp)
    ui_msg_box("",resp) 'to check the result
    sys_open(resp)


    Mick

    Comment


      #3
      RE: sys_open used with ui_get_text

      GRRRRR all the backslashes are gone. Lets try this again and I will replace the backslash with a pipe |...

      I got this work but had to enter the full path in the dialog box. In my test I entered "C:|booth.doc" - trying to parse "c:|" with the var didn't work because it doesn't like the backslash char. I didn't find the ascii equivilent or I would have tried that. Just using "C:"+alltrim(resp)would work, but I believe it would only look for the file in the current directory (didn't try it)

      dim global resp as c
      resp=ui_get_text("","File Name")
      resp=alltrim(var->resp)
      ui_msg_box("",resp) 'to check the result
      sys_open(resp)


      Mick

      Comment


        #4
        RE: sys_open used with ui_get_text

        Is there a reason why aren't you guys using UI_get_file()? Since it returns a full path you do not have to add the drive id manually.

        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: sys_open used with ui_get_text

          backslash ascii equiv is chr(92)

          Comment


            #6
            RE: sys_open used with ui_get_text

            LOL, guess that would be easier than reinventing the wheel!

            Comment


              #7
              RE: sys_open used with ui_get_text

              Thanks to both of you,Mike an Bill

              Mike, I will try your script and let you know.

              Bill, I guess "ui_get_file" brings you to the Alpha files.

              I have a long path through my server, the actual path is

              server_acme!public!bsdq!file_name.doc
              The! represents the backslash.

              with sys_open I can get as far as the directory where the files are stored, but I was trying to simply have to enter the specific file name such as sample.doc and open the file directly.

              I will study all your responses and do some trial and error tests.

              Thanks again.

              JP

              Comment


                #8
                RE: sys_open used with ui_get_text

                Jean-P.,

                Take another look at ui_get_file(). With the optional default filename parameter you can lead the user to the proper directory and allow a one click open of the file.

                An example from my testing on my local drive follows:

                rslt=ui_get_file("test","Table(*.dbf)","C:"+chr(92)\ +"cw"+chr(92)+"db"+chr(92)+"sku.dbf")


                opens the dialog box with the sku.dbf highlighted, down two directories from the top. Adding additional directories is only a matter of tacking more "directoryname"+chr(92)+ to the expression.

                Still might be easier.

                Good luck,

                Stan
                There can be only one.

                Comment


                  #9
                  RE: sys_open used with ui_get_text

                  Do you get an error message? Is the file in the C: root? You might need
                  to show the path.

                  It might look something like this: "c:"+chr(92)+"foldername"+chr(92)+
                  "file"
                  efs

                  Comment


                    #10
                    RE: sys_open used with ui_get_text

                    JP,

                    If you can use the ui_get_file() as others have suggested, this will probably be easiest and most versatile. You should be able to get any file anywhere on the system with this command. I haven't tried everything but I've tried quite a few that were not A5 files and not anywhere near the A5 directory.

                    As for your original script, I think this would work:


                    file = ui_get_text( "get number", "enter file number Ex: test.dot" )
                    result = "C:" + chr(92) + file
                    sys_open( result )

                    Since "file" is a variable, you need to leave it outside the quote marks.

                    (Of course, this assumes that the format sys_open( "C:\filename.doc" ) will work.

                    Comment


                      #11
                      RE: sys_open used with ui_get_text

                      Thanks to all of you, my script works fine:

                      You have to make sure to put the "" at the right locations and to use chr(92) instead of backslash.



                      Here is the script that works:

                      dim soum as c
                      dim result as c
                      soum=ui_get_text("soum","entrer numero")
                      result=chr(92)+chr(92)+"serveur_acme"+chr(92)+"public"+chr(92)+"soumissions public bsdq"+chr(92)+soum+".doc"
                      sys_open(result)


                      As an example when button is push all the user has to do in to enter the file name without extension such as 2149, which is is the quotation number in a word .doc file.


                      Thanks again, really appreciated.

                      Best regards

                      JP

                      Comment

                      Working...
                      X