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

function expected assignment - syntax error

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

    function expected assignment - syntax error

    Since these errors are usually a victimless crime, I update functions when I have some other reason to update them. It is nice to take care of them in case there really is another syntax error you NEED to address.

    In the first image the error seems to be because the error handler is after the end function statement.
    a5_function assignment1.PNG

    In this case it is easily corrected by moving the error trap above the end function statement.
    a5_function assignment2.PNG

    However, in a more complex scenario this would not be as easy, and I do prefer having the trap code outside of the function. Any solution?

    Bill.

    #2
    Re: function expected assignment - syntax error

    Hi Bill,
    You don't show enough of the code for me to be certain of the issue, but
    Alpha does throw an error if you instruct it to ( function myfunction as c (e as ) )
    expects to be assigned a character value (myfunction = "complete") before the end function statement.
    Gregg
    https://paiza.io is a great site to test and share sql code

    Comment


      #3
      Re: function expected assignment - syntax error

      Hi Bill

      What is wrong in using 'end' and 'resume next' statements and always have exit function at the bottom

      Doc: Resume
      Docs: End
      Alex Collier

      "The spread of computers and the Internet will put jobs in two categories. People who tell computers what to do, and people who are told by computers what to do"

      AA Builds from 5221_5152 to Pre-releases >> Deploying to IIS in AWS

      Comment


        #4
        Re: function expected assignment - syntax error

        it came in about a month ago from what I can remember, it's not declaring an error it making a warning, if you open and change in xbasic in any older component the moment you change something it will appear, the function will work as normal.
        Insanity: doing the same thing over and over again and expecting different results.
        Albert Einstein, (attributed)
        US (German-born) physicist (1879 - 1955)

        Comment


          #5
          Re: function expected assignment - syntax error

          worth a look.

          https://forum.alphasoftware.com/show...e-Xbasic-Guide
          Insanity: doing the same thing over and over again and expecting different results.
          Albert Einstein, (attributed)
          US (German-born) physicist (1879 - 1955)

          Comment


            #6
            Re: function expected assignment - syntax error

            I just noticed that the error (warning) parsing is still confused when it reported no issues in the second example. I know the full script was not shown, but the return value of import_csv is ONLY set if the code goes through import_error: So both of my examples should have been flagged with a warning.

            It can't be easy to handle all the possible code configurations. In this particular case I may drop the error reporting and use a return type of V. If I really needed the return value I could pass an argument ByRef or use a pointer argument. (Pete, I had forgotten about ByRef until I read the new xbasic guide yesterday.)

            Bill.

            Comment


              #7
              Re: function expected assignment - syntax error

              Well, I should never have doubted that Cian had covered all the bases. My statement above that both examples should have been flagged with a warning made me go back and set a value for import_csv in the case of no error. All warnings disappeared.

              Comment


                #8
                Re: function expected assignment - syntax error

                Now for something odd I noticed.
                I created the function below with the goal of testing the on error functionality.
                I was surprised that assigning a string to a numeric variable did not throw an error.
                I am using version 12.4.6.1.3 build 6232.
                Is this expected behavior or just something I am lucky enough to be experiencing?

                Code:
                FUNCTION sampleFunction AS C ( )
                on error goto ohfudge
                dim errmsg as c
                dim rnnum as n
                dim var1 as c
                dim var2 as n
                
                rnnum = rand()*25
                
                if rnnum > 15 then
                	var1 = rnnum
                	sampleFunction = "the random number is greater than 15"
                else
                '''debug(1)
                	var2 = "perfectly wrong"
                	sampleFunction = "the random number is less than 15"
                	var2 = strtran(var2,"AlphaAnywhere",34)
                end if
                
                END FUNCTION
                ohfudge:
                sampleFunction = "something went wrong"+crlf()+ERROR_TEXT_GET (error_code_get())
                Gregg
                https://paiza.io is a great site to test and share sql code

                Comment


                  #9
                  Re: function expected assignment - syntax error

                  Most always worked this way if variable type was DIMed. But many of us used to not Dim everything.
                  I can't recall about dates, but it is pretty slick.

                  dim varD as D
                  varD = "01/01/20 abc"
                  ?varD
                  = {01/01/2020}

                  of course
                  varD = "abc 01/01/20"
                  ?varD
                  = { / / }

                  Bill.

                  Comment

                  Working...
                  X