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

query_create issue

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

    query_create issue

    Hi

    I have a query which I am trying to add to a script, however, it keeps getting a 'field not found' error. If I run the query in the Interactive window then it works without complaining and the correct result is returned. If I cut and paste that query into a script running off a button (onpush) then the field not found error occurs on the qry_rd=rds.query_create() line - see below.

    I have other queries very similar to this and they work fine in a script.. Can anyone shed any light - could it be a table corruption of some sort.. (I have re-indexed and packed the table)?

    rds=table.open("racedetails")
    query.filter = "races_raceno=9"
    qry_rd=rds.query_create()
    nrecs=qry_rd.records_get()
    a5_show_variable(nrecs)
    rds.close()

    #2
    RE: query_create issue

    Futher... if I put the code in the oninit script of my form it runs fine. As soon as I out it under a button/onpush script it returns an error - weird (and frustrating!)

    Comment


      #3
      RE: query_create issue

      Plot thickens:

      If I remove the below my oninit code in the form, then the above query code works off a button on that form. However, if I use the same code in another script on a button in the same form (that contains other unrelated queries) then it fails. It is like I have hit some sort of query_create limit..

      Dim ws_nswbalin as N global
      mt=table.open("meetings")
      query.filter = "meeting_date=date()"
      query.order = "meeting_date"
      qry_dups = mt.query_create()
      nrecs=qry_dups.records_get()
      if nrecs > 0 then
      'Displays a message box (style:'Yes, No Buttons', image: 'Information symbol', id: 'msg_delit').
      DIM SHARED msgdelit_result as N
      DIM SHARED msgdelit_YES_Button as L
      DIM SHARED msgdelit_NO_Button as L
      msgdelit_YES_Button = .F.
      msgdelit_NO_Button = .F.
      title_var = "Meetings Exist for Today - Delete Existiing Details?"
      message_text_var =

      Comment


        #4
        RE: query_create issue

        Solved - query.order had a value in it from a prior query - trap for not so young players..

        Comment


          #5
          RE: query_create issue

          Is 'racedetails' a table or a set?

          Is 'meetings' a table or a set?

          If either is a set, is the other part of it?

          I'm thinking maybe you're having a naming issue with the automatic aliases Alpha Five assigns when table.open() runs. Check the docs on table.open() if this is a possibility.

          -- tom

          Comment


            #6
            RE: query_create issue

            Scott,

            good catch.

            It's hard to see something that's not there.

            Your post reminds me that others have recommended that whenever a script runs tbl.query_create() one should always fill in order and options properties fo the query object, in addition to the filter property. I'd forgotten about it until you posted your solution.

            -- tom

            Comment


              #7
              RE: query_create issue

              Scott,

              I think that's worthy of writing up for the tips section. Might help someone else down the line.
              There can be only one.

              Comment


                #8
                RE: query_create issue

                Hi Stan

                It would be good if A5 reported which field was not found rather than just reporting that a field was not found.

                Regards,
                Scott

                Comment

                Working...
                X