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



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

Argument is incorrect data type

  • Filter
  • Time
  • Show
Clear All
new posts

  • Argument is incorrect data type

    The offending line in the copy script is

    query.filter = "Dchanged>yesterday".and."isnotblank(\"photofilename\")"

    which works just fine without the .and. and following. Photofilename is C, 25, calculated as ALLTRIM(FILE.FILENAME_PARSE(PHOTO,"ne")) while Photo is an IFR - or is that IRF? Photofilename looks right in a form or browse and appears to be a simple filename with extension.

    I've tried about all the quote/slash/parens combinations, so the error message probably means what it says.

  • #2
    Re: Argument is incorrect data type

    A quoted string ends at the second quote mark. That's why the error. Alpha doesn't know what to do with the rest. Alpha might be trying to and the two strings on either side.

    You probably want

    query.filter = "Dchanged> {"+dtoc(var->yesterday)+"} .and. isnotblank(\"photofilename\")"

    if yesterday is a date variable.
    There can be only one.


    • #3
      Re: Argument is incorrect data type

      query.filter = "Dchanged>yesterday.and.isnotblank(\"photofilename\")"


      • #4
        Re: Argument is incorrect data type


        query.filter = "Dchanged>yesterday.and.isnotblank(\"photofilename\")"

        The confusion was between query.filter="this.and.that" or ="this".and."that"
        The dates are both D fields, so that much worked already.


        • #5
          Re: Argument is incorrect data type

          query.filter = "Dchanged>yesterday.and.isnotblank(\"photofilename\")"
          Is not correct, even if it may work. If it works it would only be due to yesterday being dimmed as a global variable and as an unintended consequence of how Alpha handles global variables.

          See Selwyn's post 11 and 13 in this thread.

          Better in the long run to understand the correct construction.
          There can be only one.


          • #6
            Re: Argument is incorrect data type

            Unless yesterday is not a variable ....and in live yesterday is done, fixed is not a variable anymore!
            Tomorrow, remains a variable.


            • #7
              Re: Argument is incorrect data type

              What I got from Selwyn's post was query filters cannot have variables? How do you get a value from the user without putting it in a variable?

              DIM SHARED fromdate as D
              DIM SHARED varC_result as C
              varC_result = ui_dlg_box("Backup",<<%dlg%
              Backup entries since ...?:| [%DATE;P=popup.calendar(dtoc(fromdate));I=popup.calendar%.40fromdate!fromdate_*];
              Dchanged is a D field, and I don't want to think about the dtoc confusion.


              • #8
                Re: Argument is incorrect data type

                You can have all the variables you want. You shouldn't hide them inside quotes. In certain cases Alpha will try to figure out what you meant, not always.

                query.filter = "Dchanged> {"+dtoc(var->yesterday)+"} .and. isnotblank(\"photofilename\")"

                My suggestion has three parts connected/(concatenated) by plus signs

                "Dchanged> {"
                "} .and. isnotblank(\"photofilename\")"

                The first and last parts are plain and simple text segments that do not involve variables.
                The middle part, not enclosed in quotes, is the variable - wrapped in dtoc() to make the variable's value suitable for concatenating with the other two parts.

                Since the variable is not quoted Alpha knows to use its value rather than its name in the filter.

                firstname = "Sandy"

                query.filter = "my name is firstname and I'm a dandy"

                ? query.filter
                = "my name is firstname and I'm a dandy"

                query.filter = "my name is "+quote(firstname)+" and I'm a dandy"

                ? query.filter
                = my name is "Sandy" and I'm a dandy
                There can be only one.


                • #9
                  Re: Argument is incorrect data type

                  Also see this for a better explanation. Cal used a slightly different approach with ctod() but the concept is the same.

                  There can be only one.


                  • #10
                    Re: Argument is incorrect data type


                    Sandy said
                    Dchanged is a D field, post #7

                    The DTOC() returns a character string .
                    Dchanged (Date value) and the if the Yesterday is Date value, Both are same, Date field type.

                    Do I have to convert the Yesterday variable to Character value?
                    I mean, this
                    query.filter ="dchanged >"+s_quote( var->yesterday)
                    will work or not?



                    • #11
                      Re: Argument is incorrect data type

                      That will work. S_quote() is different than dtoc(). Since I used dtoc() I included the { } in my literal strings. Dtoc() doesn't supply them in the string it returns.

                      No reason to prefer one over the other that I know, s_quote() is just easier. I learned the procedure before s_quote() was added to Alpha so I often do it the old way.
                      There can be only one.


                      • #12
                        Re: Argument is incorrect data type

                        Thanks, Stan.