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

query.create() error

  • Filter
  • Time
  • Show
Clear All
new posts

  • query.create() error

    Am building a separate table made up of data from 2 other tables. Table is zapped then it reads through the other tables to gather the data. The code is contained in a function and all that is passed through to the function is a Logical to tell it to zap the table or not zap it (this is based on a local variable that is set). Here is the strange part. This code works fine on 3 out of the 7 or 8 main forms in my app. But when run from the other forms, it will create 254 records, then throw the attached error. The function reads through the expenses table and if it finds an amount in at least one of two fields, (plan_amt or act_amt) it will look to see if there is any matching detail records. If no detail record, it uses data from the expenses table only. If the expenses table doesn't pass the amounts test, it gets the next record. In troubleshooting, I have deleted the first 50 or so records it is reading from the parent (expenses) table and try it again. When it has created 254 records, it throws this error.
    So I created a little test app with one form with one button on it and it does the same thing. Open the form test_form and press the button on it to start the process. If you get the error, open the Interactive window and do a and records_get() to see how many records it contains. I always have 254. I delete another 50 or so records from expenses and run it again and still end up with 254 records.
    The error I get is a "memory corrupt" and an "unhandled exception". Not sure this can be figured out. Don't know why it works on some of my forms and not others, or even this little plain form with one button on it. Any help would be greatly appreciated.

  • #2
    Re: query.create() error

    Ernie, digging to the bottom of your function will take more time than is available to me, but it seems to me that you're nesting queries inside loops and may be running out of query slots. Suggest you rethink your approach. You might be able to accumulate the data you need by stepping through a sorted list of records without running a querey. At minimum set query options to avoid using up query slots as the script runs through the records. Remember. Alpha multi-tasks disk activity so its a mistake to think that the script will stop while preceding instructions are finished, when those instructions tell Alpha to retrieve, sort, or query records on disk.

    Ernie, your design fetches through the Expenses table looking for records where the plan_year is 2010, plan_total is zero and Act_total is zero. I see 236 records like that. For each of these your design then tries to run a query against the exp_details table. I think you're running out of query slots. However, if I'm reading your script correctly I think you need to change the design to avoid nesting the query inside your loop.
    Last edited by Tom Cone Jr; 07-22-2010, 03:38 PM.


    • #3
      Re: query.create() error

      Thanks for the suggestions, Tom. I'll have a look at a different approach, however, I really don't think this is the case in this situation. I run the function/script from one form and I get the error. I then open another form and the script runs without error. I close that form and open another and it gets the error. I'll have to look again at how the slots are used up.


      • #4
        Re: query.create() error

        Try adding this:

        query.options = "NT"

        to new lines at

        line 64 and

        line 94

        -- tom


        • #5
          Re: query.create() error

          Tom, I apologize. I added query.options = "T" and that seemed to do the trick. Don't really understand it, but I'm sure not going to argue with it. I'll add the "N" too.
          As always, you're a great help. Thanks a bunch.


          • #6
            Re: query.create() error

            The T is for temporary meaning alpha will delete it after it's run and clear the slot if necessary. I use this as a default.


            • #7
              Re: query.create() error

              Thanks, G. I'll make it a practice from now on.


              • #8
                Re: query.create() error

                Ernie, if you fail to set the "options" explicitly before using tbl.query_create() Alpha will use the "options" that were in effect previously. The query object is a global system variable. Best to set them each time you use them. I suspect this is why your function worked in some contexts but not in others. Depending upon context, and the scripts that may have been run previously, you may have had different "Options" settings in place. Different settings led to different results. Best to set them each time you use them.


                • #9
                  Re: query.create() error

                  Up until now, I've only set:

                  The query.options is now stuck in my mind like glue. I really thought this was going to be a bear to figure out. Who would've thunk.
                  Thanks again.