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

Summary Operation - Unhandled Exception

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

  • #16
    Re: Summary Operation - Unhandled Exception

    Finian, thanks, that's an interesting commentary. I've always considered subforms only in the context of one-to-many links... and have never used them in one-to-one link settings. Will have to give this some thought. Thanks again. -- tom

    Comment


    • #17
      Re: Summary Operation - Unhandled Exception

      I hardly touched V6, V7 or V8 and perhaps something changed in there. But I'm pretty sure that in V5 and prior versions, a sub-form was a must for one-to-one links on a form. Whether that was an actual rule or the received wisdom of the time, I can't recall!
      Finian

      Comment


      • #18
        Re: Summary Operation - Unhandled Exception

        Originally posted by Finian Lennon View Post
        I hardly touched V6, V7 or V8 and perhaps something changed in there. But I'm pretty sure that in V5 and prior versions, a sub-form was a must for one-to-one links on a form. Whether that was an actual rule or the received wisdom of the time, I can't recall!
        I don't remember that rule... but I don't remember what I forget..

        Is there anyway to research your notes and verify that?
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment


        • #19
          Re: Summary Operation - Unhandled Exception

          Finnian,

          I have never had the need to use subforms, what is the correct syntax to reference objects in the subform if you need to manipulate data, how do you get a pointer to an object or field in the subform?

          Michael

          Comment


          • #20
            Re: Summary Operation - Unhandled Exception

            how do you get a pointer to an object or field in the subform
            I have not used many subforms but have you tried the Object Explorer to obtain the needed syntax? Always seems to do the job for me..... :)
            Mike
            __________________________________________
            It is only when we forget all our learning that we begin to know.
            It's not what you look at that matters, it's what you see.
            Henry David Thoreau
            __________________________________________



            Comment


            • #21
              Re: Summary Operation - Unhandled Exception

              Al:

              Notes? I don't think so. More like dredged from somewhere in the limbic cortex or some such place.

              Michael:

              The references are pretty much what you'd expect. The sub-form gets a default object name of "Form1" (which you could change) and then, put the code below in a button in the Testform2 I created.

              Code:
              thisid = alltrim(topparent:Form1:product_id.text)
              thisname = alltrim(topparent:Form1:name.text)
              ui_msg_box("","Product ID: " + thisid + Crlf(2) + "Name: " + thisname)
              
              thisid = "";thisname = ""
              t = table.get("Vendor")
              thisid = alltrim(t.product_id)
              thisname = alltrim(t.name)
              
              ui_msg_box("","Product ID: " + thisid + Crlf(2) + "Name: " + thisname)
              so you have two ways, via object or table reference.
              Finian

              Comment


              • #22
                Re: Summary Operation - Unhandled Exception

                Originally posted by Finian Lennon View Post
                Al:

                Notes?
                Sorry forgot my ;)
                Al Buchholz
                Bookwood Systems, LTD
                Weekly QReportBuilder Webinars Thursday 1 pm CST

                Occam's Razor - KISS
                Normalize till it hurts - De-normalize till it works.
                Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                When we triage a problem it is much easier to read sample systems than to read a mind.
                "Make it as simple as possible, but not simpler."
                Albert Einstein

                http://www.iadn.com/images/media/iadn_member.png

                Comment

                Working...
                X