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

ui_get_file path

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

  • ui_get_file path

    How do I select the path for the ui_get_file operation.

    Right now, it defaults to the "My Documents" folder.

    Thanks.

  • #2
    RE: ui_get_file path

    John,

    To set it to a directory with no file selected, use something like

    default="c:|Program Files"+chr(92)+"."
    ui_get_file("title","*.dbf",default,"")


    To set it to a directory with a file listed in the dialog box, use something like

    [b]default="c:|Program Files"+chr(92)+"filename"
    ui_get_file("title","*.dbf",default,"")
    Regards,

    Ira J. Perlow
    Computer Systems Design


    CSDA A5 Products
    New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
    CSDA Barcode Functions

    CSDA Code Utility
    CSDA Screen Capture


    Comment


    • #3
      RE: ui_get_file path

      Careful Ira, your DOS roots are showing.
      There can be only one.

      Comment


      • #4
        RE: ui_get_file path

        Hi Stan,

        If my roots are showing, I guess I'll have to DYE them
        (Since everyone knows that DOS has DIEd)! :?)

        Regards,

        Ira J. Perlow
        Computer Systems Design & Associates
        [email protected]
        Regards,

        Ira J. Perlow
        Computer Systems Design


        CSDA A5 Products
        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
        CSDA Barcode Functions

        CSDA Code Utility
        CSDA Screen Capture


        Comment


        • #5
          RE: ui_get_file path

          Hey,

          If DOS is dead, why do we still have page faults and windows "resource" problems. Don't you just love that 640K base memory restriction? We haven't come very far, baby!
          There can be only one.

          Comment


          • #6
            RE: ui_get_file path

            Just add a default file:

            ui_get_file( "FILE", "All(*.*)|Apps(*.Exe)|", "C:DATA*.*" )

            will automatically show all files in the C:DATA directory.

            NOTE: The "file type string" ("All(*.*)|Text(*.Exe)|" in this case) is important. It determines which files appear in the popup window. The default name only determines the text which is 'typed' in the popup window's "File Name" box. If the default file is abc.dbf and the type string is *.exe, then the text "abc.dbf" will appear in the "File Name" box but it will not appear in the list of files.

            If there is an asterisk anywhere in the default name, then no name will appear in the "File Name" box of the popup window.

            EXAMPLE:
            ui_get_file( "FILE", "All(*.*)|Apps(*.Exe)|", "C:DATAg*.exe" )

            would show all files (and folders) in the C:DATA directory but there would be no filename in the file selection box.

            (Wow, I got confused just writing this - hope it makes sense!)

            Comment


            • #7
              RE: ui_get_file path

              OK, I got sidetracked so by the time I got back and finished this there were a bunch of responses.

              Also, I forgot to include the backslashes in my ui_get... lines so here are the corrections:

              ui_get_file( "FILE", "All(*.*)|Apps(*.Exe)|", "C:\DATA\*.*" )

              EXAMPLE:
              ui_get_file( "FILE", "All(*.*)|Apps(*.Exe)|", "C:\DATA\g*.exe" )

              Comment


              • #8
                RE: ui_get_file path

                Thanks everyone, I'll give it a try this afternoon.

                I've got to say this message board is great!!

                Comment


                • #9
                  RE: ui_get_file path

                  Hey, back in the CPM days (before MPM and CPM 3.0) we were limited to just 64k.

                  But heck, we've have come a long way. Now we can cause Page faults and windows "resource" problems at above Ghz speeds.

                  And now we can waste my 75 Gig Hard drive space at incredible rates (The next version of Office probably requires 300 Gigs!). But while my first rotational media was a 72k North Star floppy drive that cost about $600, my 75 Gig Hard drive (50k free space currently! - :?) ) was cheaper than that!

                  Oh well. We can't halt the progress of technology.

                  --Ira
                  Regards,

                  Ira J. Perlow
                  Computer Systems Design


                  CSDA A5 Products
                  New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                  CSDA Barcode Functions

                  CSDA Code Utility
                  CSDA Screen Capture


                  Comment


                  • #10
                    RE: ui_get_file path

                    That brings back old memories. My first computer was a Vector Graphic, 4Mhz Z80, with 2 350 floppies. I remember standing with a client once, explaining what was happening, (as a distraction from the time it took,) while we all waited patiently for the computer to boot, and then the Memorite word processor to boot, circa 1980.

                    They had just paid about 13,000 for the computer, Memorite, Peachtree written in MBasic IV, and a printer with characters on a wheel - can't remember the name anymore for that type. Hail, printers were around 3 to 5,000 in those days.
                    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


                    • #11
                      RE: ui_get_file path

                      Daisywheel.

                      Oops, shows how old I am.

                      Stan
                      There can be only one.

                      Comment


                      • #12
                        RE: ui_get_file path

                        Oh boy. I wrote my first program with a paper clip... First you punched out the program, then the data, then you went to the building with the computer and passed the pile of cards through the little window to the people in the climate controlled room. The next day you got the print outs -if there were bugs, you had to correct the faulty cards and resubmit. This was 1975, I think. Then in 1980 I got to "work" on a TRS80 from radioshack running visicalc and writing programs in some variety of Basic. Storage was on a cassette tape recorder(!?). I kinda feel the wheel has turned as we now use CD's the same way...

                        Comment


                        • #13
                          RE: ui_get_file path

                          I never thought about this until I read Stephen's comments about using the punch cards in 1975. The first program I wrote was in 1967 at GMI (now Kettering University) and we had the same punch card system - including the window to the climate controlled room. That was an 8 year time period. Now think about how far PC's have come in the last 8 years. Wow! Where will we be in another 8 years?

                          Comment


                          • #14
                            RE: ui_get_file path

                            Cal,

                            We'll be able to cause Page faults and windows "resource" problems at above Thz (Tetrahertz) speeds.

                            And we'll be able to waste our 75 Tet Hard drive space at incredible rates (The next version of Office probably will require 300 Tets!).

                            And the dialup phones will have increased to 64k! (DSL will have come and died I suspect). But with broadband access in the Gigabit range, we can waste our time on the internet at much higher speeds. :?)

                            Interestingly, the way technology has progressed with computers and phones cell technology, we are closer to Star Trek's universe than that of 2001: A Space Odyssey.

                            --Ira
                            Regards,

                            Ira J. Perlow
                            Computer Systems Design


                            CSDA A5 Products
                            New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                            CSDA Barcode Functions

                            CSDA Code Utility
                            CSDA Screen Capture


                            Comment


                            • #15
                              RE: ui_get_file path

                              I'm familiar with terahertz and terabyte being 1024 times a gigahertz and gigabyte, respectively, but tetra- I'm not sure. Could you enlighten me as to the multiplier involved?

                              Speaking of hertz, how is Heinrich these days?
                              There can be only one.

                              Comment

                              Working...
                              X