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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Button to find by name

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Button to find by name

    I'm struggling to learn XBasic and have been helped a lot by the article by Dr. Wayne "A General Purpose Find by Key." I have a table indexed on "loan_no" and "borr_last." The button I created for find by loan number works great but I can't get the name find to work. I have a line like this:

    query.filter="between(borr_last,reply,'99999999999')"

    but I'm at a loss to understand the 9's. Are they meant to be place holders, so I need to have as many as there are characters in my field? My longest loan number is 7 so I used 7 9's but, to be honest, I have no idea why.

    Also, how can I "protect" fields on a form so the user can't change them? Can't seem to find the answer to that. These are all fields which are imported from a text file daily.

    Can anyone help me get past these last stumbling blocks?
    Tags: None
    #2
    RE: Button to find by name


    Jane

    Here is a button script that I use to find a person by last name...

    ''xbasic
    'prompt the user for a name to find, returns a character string
    name_found = ui_get_text("Search for Last Name", "Enter last Name")

    p=obj("Personal_info")'this sets a pointer to form
    P.index_set("last_name")'set the index to last name
    p.find(name_found) 'find the record that matches the name_found variable
    ' you can change the index after the record is found
    P.index_set("account")


    One way to prevent a field from edits is to put the form in edit mode then right click the field(S) & select properties. Check the box "disable" as shown below.

    Comment

      #3
      RE: Button to find by name

      Bless you! Problem solved! I aspire to be able to answer questions one day, not ask...

      Side note: what the heck are we doing working?

      Many thanks,
      Jane

      Comment

        #4
        RE: Button to find by name

        Actually Jane the example I gave you for preventing edits was on a calculated field. In the properties of character, date, numeric.... there is a "read only" option that might be a better choice for preventing changes.

        You can also prevent changes with an xbasic script attched to the "OnChange" event of the field. Hope I haven't added to the confusion Jane?

        ''XBasic
        :formname:fieldname.Disable()

        end

        Comment

          #5
          RE: Button to find by name

          Not at all, I have come to realize that there are many ways to accomplish things in A5, it's just a matter of finding the best one...

          Out of curiosity:

          What would be the difference between making a field on a form "read only" and disabling it?

          And one last question for the night: Main form has "borrower_info" as parent, embedded browse to show loan payments made. Quite often when entering in a loan payment I get a "not an open index" message. If I exit the form and open it up again it's fine. Any ideas on this? I have two indexes (aka indices, what an unnatural word!) "loan_number" and "pay_date." Loan number has always been the primary up to this point.

          I can't thank you enough for your help!

          Jane

          Comment

            #6
            RE: Button to find by name

            Jane,

            The "read only" field property can receive focus, that is you can tab to that field but you cannot edit it. With the "disable" field propery the field is skipped in the tab order. So for instance if you have a global variable for the current user, if the field can receive focus then in the OnArrive event you can have a script that checks the value of the global variable "USER" & allow certain users "edit" rights to those fields that are "read only" but if they are "disabled" you would want to have a button with a password that would change the "disable" property of the field to "enable" if the password was entered correctly.

            I need to give your 2nd question a little more thought, but off the top of my head, check the indexes in the primary table of the set as well as the child table. Rebuilding the indexes as well as compacting the database might improve the situation....

            Comment

              #7
              RE: Button to find by name

              Doug, I think you were getting a little fuzzy that late at night. What you said is correct but it gives the impression that the only way to modify the property of a 'disabled' field is by putting a button on the form.

              A user can't edit a field that is either "read-only" or "disabled" unless there is a button or other means* to change the mode of the object.

              The key difference, as you mentioned, is "receive focus". So, if a field is 'read-only', it can still receive focus and the user could still click on that field to perform a 'quick sort' or 'quick filter'. It will also be included in the tab order by default. If the field is disabled, it cannot receive focus even if clicked on directly.


              *Other means: In applications where I have multiple user levels and want only certain users to have access to a field or button, I use an OnInit script which checks the user's security level (which is assigned to them in a log-on script when they start the application) and modifies the object(s) properties accordingly. These properties could be either 'read-only' or 'disabled' as well as many others such as font and color.

              Comment

                #8
                RE: Button to find by name

                Hi CAl...

                If you tell me "THAT" never happens to you, I will tell you that you are getting entirely too much sleep!

                Thanks for the heads up, you are right of course, in both cases. I was pretty tired & I did lead Jane to believe that the button was the only solution.....

                The OnInit event is in most cases the best place to assign rights to a form! Provided that the form is not left open in the background and a new user is able to access the login form...

                Thanks for the assist Cal....

                Comment

                Previous template Next
                Working...
                X