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

disappearing fields in xbasic query

  • Filter
  • Time
  • Show
Clear All
new posts

  • Al Buchholz
    Re: disappearing fields in xbasic query

    Is the table jobbook part of the set(or only table) that the form is based on?

    build a query and save it, then run that query.

    In view mode, query, query by expression, save the query.

    In Design mode: Make a button - action scripting - Index/Sort - Run Saved Query (or use the code generated in your script)

    Leave a comment:

  • DaveM
    Re: disappearing fields in xbasic query

    Try a compact before all the work?

    Leave a comment:

  • mariusm
    Re: disappearing fields in xbasic query

    Thanks Al, this is getting strange.
    msgbox(query.filter) gives me a correct filter - e.g. ((j_year = "2016").and.(j_month = "Jan").and.(j_week = "1"))
    but the query doesn't run.
    However, if I place a button with the very same script on a different random form, it runs without a hitch, using the variables set on this form. The script is bigger (236 lines), not just a query, but it is the query that fails. I made a button just with the query and nothing else, and it still fails on this form.
    I am beginning to wonder if I don't have a corrupt form, I will rebuild it from scratch and try again.

    EDITED to say that, yup, it was a corrupted form. A new form with the exact same script runs with no problems.
    I wonder if it's a compatibility problem, the form was originally built in version 11 of Alpha.
    Last edited by mariusm; 04-13-2016, 06:08 PM.

    Leave a comment:

  • Al Buchholz
    Re: disappearing fields in xbasic query

    Use a debug(1) to look at the value of query.filter after it is set and prior to qry3 = tbl3.query_create()


    use msgbox(query.filter) after the query.filter value is set.

    Leave a comment:

  • mariusm
    started a topic disappearing fields in xbasic query

    disappearing fields in xbasic query

    I have this weird problem in an inline xbasic script.
    Part of it includes a query,

    tbl3 ="jobbook")
    query.filter = "((j_year = "+s_quote(var->vvYear)+") .and. (j_month = "+s_quote(var->vvMonth)+") .and. (j_week = "+s_quote(var->vvWeek)+"))"
    qry3 = tbl3.query_create()

    The three variables are global variables, and the fields all very definitely exist in the table.

    What happens is, when I first run the query, I get an error saying qry3 = tbl3.query_create() No such field.
    BUT if I close the form and re-open it, the query runs with no problem. If I change the value of a variable, it again doesn't run unless I close and reopen the form.
    I thought my variables are disappearing, but if I check for them in the code editor, they are there. I do not have other variables with the same name anywhere in my application. I tried dim-ing the variables again in the script, just in case - it didn't help. I tried xbasic_wait_for_idle() in case there was a timing issue, but there wasn't. I tried refreshing the form before running the script. No joy.
    I tried the query with and without s_quote, it does the same thing either way.
    So I am out if ideas.
    Have any of you run across this? How can I get around it?
    Last edited by mariusm; 04-13-2016, 03:20 PM.