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

file.exists() problem

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

  • file.exists() problem

    File.exists() does not seem to work properly in A5V4.03 build 230. In one of my scripts, I have two variables called current_path and bitmap_file. They contain the name of the current folder (including the drive letter and the final backslash) and a bitmap file which exists in the folder.

    My script includes the following statement:

    result = file.exists(current_path + bitmap_file)

    This evaluates correctly when the length of current_path is less than 29, but always returns .F. when the current path contains 29 or more characters.

    If I explicitly name the file e.g. result = file.exists("c:worka5v4clientsurcadministrationblank.bmp")

    the result evaluates correctly.

    Does anyone know why this happens?

    Thanks,
    Tony

  • #2
    RE: file.exists() problem

    I think that using :A5.get_path()+"filename") would work better than current_path. I think that your problem is one of having the correct path.

    Nick

    Comment


    • #3
      RE: file.exists() problem

      Tony, I wonder if this is a backslash issue? Does your variable include the trailing backslash (which is needed as a separator between the path and the filename)? It is possible you're putting it in when you use the explicit constant, and leaving it out by accident when you concatenate the variable and the filename.

      Backslashes are tricky, because they are the A5 line continuation character, so you might need to actually build the string like this:

      var->current_path + chr(92) + bitmapfilename

      -- tom

      Comment


      • #4
        RE: file.exists() problem

        Tom & Nick

        Thanks for your replies. I use a5.get_path to get the value of current_path. My script includes backslashes in the right places - I have stepped through the script using the debugger and watched the values of the variables, and they are all OK.

        The script works perfectly when the total length of the path is up to 28 characters, but gives an incorrect FALSE result when the path is longer than 28 characters.

        Tony

        Comment


        • #5
          RE: file.exists() problem

          Tony, using vers 4.03 (build 230) I cannot replicate the problem you are seeing.

          Here's what I see in the Interactive Editor:

          currpath = "C:A5v4AdvancedDataEntryEnhancedJimUrbanski"
          filename = "Mainmenu.dbf"
          resultstring = if(file.exists(currpath+filename),"Found it","Cannot see it")

          ?currpath
          = "C:A5v4AdvancedDataEntryEnhancedJimUrbanski"
          ?len(currpath)
          = 45.000000


          ?filename
          = "Mainmenu.dbf"
          ? len(filename)
          = 13.000000

          ? len(currpath+filename)
          = 58.000000


          ?resultstring
          = "Found it"


          In my setup the file MainMenu.dbf is actually present in the specified folder, and the function file.exists() found it.

          The length of the path to the file exceeds the 28 character limit you are seeing.

          Am I missing the point?

          -- tom

          Comment


          • #6
            RE: file.exists() problem

            Darn. I forgot that this board eats the backslash characters, let me try again.

            Here's what I see in the interactive editor, with pipes substituted for the backlashes I actually used:

            currpath = "C:|A5v4|AdvancedDataEntry|EnhancedJimUrbanski"
            filename = "|Mainmenu.dbf"
            resultstring = if(file.exists(currpath+filename),"Found it","Cannot see it")

            ?currpath
            = "C:|A5v4|AdvancedDataEntry|EnhancedJimUrbanski"
            ?len(currpath)
            = 45.000000


            ?filename
            = "|Mainmenu.dbf"
            ? len(filename)
            = 13.000000

            ? len(currpath+filename)
            = 58.000000


            ?resultstring
            = "Found it"

            Comment


            • #7
              RE: file.exists() problem

              Tom,

              It works OK for me in the interactive window or in a script when the file is named explicitly in the file.exists statement, e.g. result = file.exists("c:/aaaaaaaa/bbbbbbbb/cccccccc/filename.dbf")

              It always gives result = .F. when the script holds the path/file name in variables and the path is >28 characters. This applies both in a script and in the interactive window, e.g.

              bs = chr(92)
              current_path = :a5.get_path() + bs
              filename = "filename.dbf"
              result = file.exists(current_path + filename)

              Comment


              • #8
                RE: file.exists() problem

                Tony, that's odd.

                As you can see from my example, I used variables in the interactive window to hold the path and filename. The length of the path variable is greater than 28.

                Can you post a working example that illustrates the problem?

                -- tom

                Comment


                • #9
                  RE: file.exists() problem

                  Tony, maybe there's something goofy in your script?

                  Here's an example that seems to work just fine with long path and filename strings.

                  Unzip the attachment to a separate folder.
                  Do not mix it with your development work.

                  Begin with form "Names1"

                  -- tom

                  Comment


                  • #10
                    RE: file.exists() problem

                    Tom,

                    Thanks, I will look at it later today

                    Tony

                    Comment


                    • #11
                      RE: file.exists() problem

                      Tom,

                      I have found the error in my script. The name of the file is stored in a field (field length = 255), so it has trailing spaces. The script works OK if I use:

                      result = file.exists(current_path + trim(bitmap_file))

                      The original script always worked OK when its application was in its original location, and only failed when I copied it to a new folder with a longer name.

                      I have experimented with the form you sent to me, and added the following lines to the "test file.exists" button's script:

                      num = val(ui_get_number("Enter number" , "number of spaces" ))
                      tfile = tfile + space(num)

                      The test gives a correct result when the total number of characters (path + file name + trailing spaces) is less than 260, but evaluates as .F. when the length is >= 260. I assume that this is related to Windows 98's path + file name limit of 255.

                      Thank you for all your help with this.

                      Tony

                      Comment


                      • #12
                        RE: file.exists() problem

                        Tony,

                        Ahhh, the old trailing blank spaces bug-a-boo. I've been bitten by that rascal many, many times myself so I can sympathize. Glad you got it going.

                        -- tom

                        Comment

                        Working...
                        X