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

Can't figure it II

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

    Can't figure it II

    If you have not followed this topic the problems are in the topic "Can't figure it"


    I have installed A5V4 on another machine as a test

    The script works fine.

    When my machine crashed last week I took the opportunity to install Windows 2000. Could this be the source of my woes?

    #2
    RE: Can't figure it II

    Bruce,
    I suspect your problem may be corrupted data or Win2000. If you search the forum for Win2000 or Windows 2000, you will find a number of posts. It appears Win2000 doesn't always work as advertised(what a surprise).

    Incidentally, I created a table with the same field names, browse name, and dummy values as appear in your example. Then I cut and pasted your script. It didn't find any records, even when the search string exactly matched the field value. While your script looks fine, I have found that running multiple operations in xbasic doesn't always work as expected. I have a few apps where I have split each operation into separate scripts and then run them in sequence. In one case, I had to close and reopen each table after each operation to get reliable results.

    The script I posted worked both on exact matches and wildcards. It also only fetches once to set search to either T or F. This will be twice as fast as your origianl script, which may bve important with large tables.

    By the way, the job_name is a character field and search is a logical field, right?

    Jerry

    Comment


      #3
      RE: Can't figure it II

      A little test shows your origianl script will work if jo_name is a character field and contains either all numbers or capital letters. This works even if the search string is in small letters or uses wild cards. It fails if the field contains lowercase characters. If you change the following line

      if like(tsearch,jn.job_name)

      to
      if like(alltrim(lower(tsearch)),alltrim(lower(jn.job_name)))

      then your script seems to work every time. You still have a problem if no records are found.

      Jerry

      Comment


        #4
        RE: Can't figure it II

        I reinstalled A5V4 and all is fine again.


        Is there a way to automatically have the wildcards in the front and back.

        Comment


          #5
          RE: Can't figure it II

          tsearch="*"+alltrim(lower(tsearch))+"*"

          before the

          if like(alltrim(lower(tsearch)),alltrim(lower(jn.job_name)))

          should do that.
          There can be only one.

          Comment


            #6
            RE: Can't figure it II

            This line causes A5 to crash
            tsearch="*"+alltrim(lower(tsearch))+"*"
            After restarting A5 the script does not work again!

            I give up

            Comment


              #7
              RE: Can't figure it II

              Bruce,

              Sorry, don't know why that would cause a crash.

              Stan
              There can be only one.

              Comment


                #8
                RE: Can't figure it II

                Bruce
                Don't know what your problem is, but I tried

                tsearch="*"+alltrim(lower(tsearch))+"*"

                and it worked fine on a test search using your original script. Still using Win2000? I doubt the problem is your script. Does this problem occur with every computer using your script? In any case, I sometimes add the following to trap errors in a script.

                on error goto error_handler
                '// Script main body
                end
                error_handler:
                msg = error_text_get(error_code_get())+chr(10)+chr(13)+"Error occured at line "+str(error_line_number_get(),4,0)
                ui_msg_box("Error",msg)

                Jerry

                Comment

                Working...
                X