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 Find Bug

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

    File Find Bug

    The following script crashes A5 every time if a filename has more than one period in it (e.g. "sample.test.txt"):

    ''XBasic:

    ON ERROR GOTO ERROR_MAN

    vBackSlash = chr(92)

    vPath = "c:" + vBackSlash + "junk3" + vBackSlash + "*.*"
    vFiles = filefind.first(vPath)

    while .not. vFiles.eof()
    ''''
    vFiles.next()
    end while

    END
    ERROR_MAN:
    ON ERROR GOTO 0
    END


    Is there a work around?
    Peter
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com



    #2
    RE: File Find Bug

    Peter, I think filenames with two periods are very rare. I guess it's my old DOS experience showing itself, but I'm a bit surprised that it's a valid filename in the first place. Doesn't such a filename cause Windows trouble with File Association processes? I guess I'm wondering if it wouldn't be too crazy to insist that the user limit themselves to a single period. Though I know this probably bucks the trend of 'the end user rules' or 'anything they want, they get'.

    I'll be monitoring this thread, to learn how truly old fashioned my thinking may be.

    -- tom

    Comment


      #3
      RE: File Find Bug

      Peter, I'm going to do some testing, but I'll bet the problem is with the filespec you're using. '*.*' The wildcard probably covers everything except periods, for good reason. If it included the period it couldn't find the extension.

      I'll bet your system is not running windows 95 either, right?


      -- tom

      Comment


        #4
        RE: File Find Bug

        Hi Tom,

        That's an interesting observation regarding the *.*. I'm using WIN ME. My understanding is that Windows looks at the last period in the filename to determine the extension and file association. More than one period is fairly rare, but it is used here and there. I think cookies, among others, typically use more than one period.
        Peter
        AlphaBase Solutions, LLC

        [email protected]
        https://www.alphabasesolutions.com


        Comment


          #5
          RE: File Find Bug

          Peter, using Win 98 SE and vers. 4.5 of Alpha Five I've confirmed your observations. Filefind.first() causes A5 to crash hard if the folder contains a filename with more than one period in it.

          I've tested filespecs "*.*", "*", and "*.*.*" and they all crash. I don't see an easy workaround, that would not require renaming such files before running your script...

          Would be nice if an error were returned, instead of the crash. However, if fixing this causes other work to slow down, I'd be hard pressed to recommend that they spend the energy on it. For me it would be sufficient to indicate in the docs that filefind.first() only works with filenames which contain no more tha one period.

          Comment


            #6
            RE: File Find Bug

            Tom (et al),

            Perhaps things like quotes around the file spec might work. How about a blank or null spec. Or try just a single "." (which is an alias for the whole directory. Perhaps using "????????".???" or similar might work.

            Also, this is not the only bug. If no attributes on the file are present, the file will not be found. There is a new method in Ver 5 that fixes this problem and is the preferred method (according to Selwyn).

            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


              #7
              RE: File Find Bug

              Ira, I'm sorry I wasn't clearer. Each of the filespecs I tried were enclosed in double quotes. I also tried a null spec, consisting of two double quotes without a blank space. Alpha Five crashed on each. Did not try combinations of question marks...

              -- tom

              Comment


                #8
                RE: File Find Bug

                Tom,

                Try it with chr(34)+pathname+chr(92)+"*.*"+chr(34)

                Substitute other stuff for the *.* as well. The double quotes tell Windows that it is a literal filespec including spaces and maybe extra periods. Just an idea.



                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


                  #9
                  RE: File Find Bug

                  Ira, the path to the folder is working fine.

                  What we're struggling with is the argument to the filefind.first() method.

                  It takes a character string which consists of a desired filespec, like

                  "*.dbf"
                  "*.*"
                  "*.d??"

                  and so on.

                  the argument is itself enclosed in parentheses, as in

                  filefind.first("*.dbf") or
                  filefind.first("*.*")

                  where do you suggest I insert the extra quote marks?

                  -- tom

                  Comment


                    #10
                    RE: File Find Bug

                    Tom,

                    I agree, Alpha shouldn't slow down their effort to get ver. 5 out. Looks like it has already been solved according to Ira. All the more reason to speed up release 5.

                    Peter
                    Peter
                    AlphaBase Solutions, LLC

                    [email protected]
                    https://www.alphabasesolutions.com


                    Comment


                      #11
                      RE: File Find Bug

                      Tom,

                      Try setting path to make the directory the current directory. (I forget the Xbasic command). This will eliminate the path as in issue. Then put the CHR(34) around the filespec as in

                      filefind.first(chr(34)+"*.dbf"+chr(34))

                      Try other variations including the "."

                      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

                      Working...
                      X