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

Code Help

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

    Code Help

    I have the following code attached to a button on a form. It works with version 7 but gives the attached error under version 8.

    Anyone suggest how to change it to make v8 like it?

    Thanks

    Code:
    'Date Created: 13-Jan-2004 07:11:25 PM
    'Last Updated: 14-Jan-2004 06:46:59 AM
    'Created By  :
    'Updated By  : 
    inv_fnd = ui_get_text("ENTER INVOICE NUMBER","Enter the invoice number to find...") 
    IF inv_fnd = "" 
       END 
    END IF 
    inv_fnd = padl(inv_fnd,8,"0") 
    'parentform.index_setexplicit("<Invoice_No>") 
    parentform.find(inv_fnd)

    #2
    Re: Code Help

    try:
    dim inv_fnd as c 'at the top of the code

    Comment


      #3
      Re: Code Help

      Mark,

      1) are the form's records sorted on the invoice number field when the script runs?

      2) in your table structure is the invoice number numeric or character (data type) ?

      Comment


        #4
        Re: Code Help

        Originally posted by G Gabriel View Post
        try:
        dim inv_fnd as c 'at the top of the code
        This didn't work - thanks

        Comment


          #5
          Re: Code Help

          Originally posted by Tom Cone Jr View Post
          Mark,

          1) are the form's records sorted on the invoice number field when the script runs?

          2) in your table structure is the invoice number numeric or character (data type) ?
          The form is sorted by the invoice field and it is defined as a character field.

          If it matters, the invoice number field is displayed via an embedded browse.

          Thanks

          Comment


            #6
            Re: Code Help

            Mark, is the form based on a set of tables? Does the embedded browse display records from the parent table or from a child table? -- tom

            Comment


              #7
              Re: Code Help

              Originally posted by Tom Cone Jr View Post
              Mark, is the form based on a set of tables? Does the embedded browse display records from the parent table or from a child table? -- tom
              The form is based on a set and the embedded browse displays records from the parent table.
              Thanks

              Comment


                #8
                Re: Code Help

                Mark,

                I don't see anything else to suggest other than to upload a copy of the database with instructions for us to follow to see the problem. With a bit of study perhaps we can explain what's happening... or, in worst case, we could confirm a bug to be submitted to Alpha.

                Comment


                  #9
                  Re: Code Help

                  Originally posted by Tom Cone Jr View Post
                  Mark,

                  I don't see anything else to suggest other than to upload a copy of the database with instructions for us to follow to see the problem. With a bit of study perhaps we can explain what's happening... or, in worst case, we could confirm a bug to be submitted to Alpha.
                  I just made an interesting discovery. If I open the form from the control panel, the button works fine. If I open the form from the Main Menu, the button gives the above error.

                  Does that give any other indication of what might be wrong with it?

                  Thanks

                  Comment


                    #10
                    Re: Code Help

                    Ok - I figured it out - and as always, it was my fault.

                    In the form properties, I have it set to filter records to only show:
                    Invoice_No>"00015000"

                    The button on the main menu was also set to use the same filter when opening the above form. I removed this from the button on the main menu and it works fine.

                    I appreciate all the help.

                    Comment


                      #11
                      Re: Code Help

                      Mark:
                      Although you say you solved the problem and it was your fault, I am not so convinced. I think you are being hard on yourself.

                      I tried a simillar script on a test form with the same error message that does not make any sense! Furthermore, the filter should not matter. If parentform.find() cannot locate the exact match, it will locate the closest one. So, most likely the filter is not the issue.

                      If it re-appears, I would report it as a bug. I believe alpha is not recognizing the variable in the first execution and whatever you did, although might have nothing to do with that, only worked as the variable with it's scope & definition became availble on subsequent executions which might have led you to believe that whatever you did has fixed the issue.

                      I hope, for you sake, I am wrong, but none of these make any sense.

                      Comment

                      Working...
                      X