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

Parent/Child querying by child field

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

    Parent/Child querying by child field

    Hello all,

    I have a parent/child set that I need to query by a date field that is in the child table. I am able open and iterate through a set using a pointer to each table, as shown in the documentation, but am I not sure how to filter by a value of a field in the child table.

    One alternative seems to be to open the parent and child tables, and then using tbl.relation_add to create a master/child relationship. When I invoke that function I get an error "Not an open index". The relevant code is below, executed against the Alpha's Sports demo database:

    Code:
    parenttbl = table.open("invoice_header.dbf")
    childtbl = table.open("invoice_items.dbf")
    
    child_index = childtbl.index_get("Invoice_Nu")
    relation.link_type = LINK_MANY
    relation.index_child = child_index
    relation.order_parent = "INVOICE_NUMBER" 
    relation.ref_integrity = 0
    parenttbl.relation_add(childtbl)
    The error happens at the parenttbl.relation_add invocation. I have tried different values for the argument in index_get but the error is always the same.

    So, two questions:

    1) What is the proper way to query a child table that is part of a set based on values in one of the child's fields?
    2) What does "Not an open index" mean in this context?

    Thanks,

    Armando

    #2
    Re: Parent/Child querying by child field

    In a Set, build the Query using the built in Query option but query the records at the Child table level. The automatic setting is Cross Level. Change that to the Child table.
    Then, run the query and save it.
    Then, change the query so the you can use a variable if you wish for a specific date.
    This is the code which the Query builds using today's date in a "person/date" set;

    Code:
    dim filter as c
    dim order as c
    dim options as c
    dim description as c
    dim show_all_flag as L
    dim layout_name as c
    dim layout_type as c
    filter = "date = ctod("23/01/2019")"
    order = "recno()"
    options = ""
    description = "Saved Query: Q_Date"
    show_all_flag = .f.   'user cannot turn off the query
    layout_type = "browse" 'to open a form, set this to "form"
    layout_name = ""   'This will open the default layout. You can also specify a named layout here
    dim args as sql::arguments
    if eval_valid("arguments") then 
    	if typeof(arguments) = "P" then
    		 args = arguments 
    	end if 
    end if 
    a5_open_layout(layout_type,layout_name,"persondate.set",filter,order,description,options,show_all_flag,args)
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    Apologies to anyone I haven't managed to upset yet.
    You are held in a queue and I will get to you soon.

    Comment


      #3
      Re: Parent/Child querying by child field

      Thank you Ted, I'll experiment with that.

      Armando

      Comment

      Working...
      X