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

Wonderful .. Data from kids into comma delimited string and stuffed into parent table

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

    Wonderful .. Data from kids into comma delimited string and stuffed into parent table

    This is a combination of having learned a couple of wonderful things and building them together to do something great.

    From post #5 of this thread about converting a string of data from kid records (thank you DavidK)

    http://msgboard.alphasoftware.com/al...limited-string


    sqlSelect = "DECLARE @EmpId VARCHAR(1000); SELECT @EmpId = COALESCE(@EmpId + ',', '') + EmployeeId FROM Employees; select @EmpId"
    I built a Stored Procedure in SQL based on applying that process. It looks at the child table, and makes a string of the data, and then I update the parent table based on the string.


    And I'm using the Code.ServerSide.Event.OnAfterSQLCommandExecute - which fires of my stored procedure to update the parent table, after I insert or update a child record.



    now, does anyone want to come prepare my house for putting it on the market, so I can continue to build my UI????
    MSQL since 2010
    A5V11 since Feb 2012

    #2
    Re: Wonderful .. Data from kids into comma delimited string and stuffed into parent t

    Glad you figured out something that worked for you!

    I also have an app with a client and then related records for each other member of the household. I keep statistics on the members of the household in the client record so every time something changes I have to update the statistics. I do that by Xbasic code in the after update event. Happy to share this code with you or anyone who might need an example. I took it from the Access version of my app and modified for xbasic. Runs fast. I found after I posted the updates to the client record, that the Detail section showing the statistics was refreshed automagically.

    Bob
    Bob Alston
    -------------------------------------------------------------------
    http://webpages.charter.net/bobalston/bob1.htm
    Alpha five v11 Tips

    Comment


      #3
      Re: Wonderful .. Data from kids into comma delimited string and stuffed into parent t

      thanks Bob -

      I'm trying to stay away from xBasic as much as I can, and let SQL handle the workload whenever possible..... I'm crunched for time and figure I'll go back and learn more xBasic once I have a functional UI

      Does your xBasic code put hard numbers into actual columns in a parent table? I don't put summary statistics into parent tables; what is the advantage of doing so?

      I handle summary statistics of that nature via views (or stored procedures), and then use the views to 'drill down' to the detail.

      The info I was working with was character based; I was stuffing a concatenated string of words into the header table.... actually, now that I think of it, now that i have DavidK's nifty code, I probably don't even need to store the string. I can just create it in my view, as needed.... I'll have to compare speed.
      MSQL since 2010
      A5V11 since Feb 2012

      Comment


        #4
        Re: Wonderful .. Data from kids into comma delimited string and stuffed into parent t

        I imagine that stored procedures is the best method of doing this. When I built my app originally in Access, stored procedures weren't available. And I knew how to code in basic. The only advantage I can see is not having to do the computations at run time/each time the data is viewed. But for a small amount of data, the elapsed time would be quite small.

        My background includes a lot of programming in multiple languages, including Basic and VBA. so Xbasic is just a new dialect.

        Regards,

        Bob
        Bob Alston
        -------------------------------------------------------------------
        http://webpages.charter.net/bobalston/bob1.htm
        Alpha five v11 Tips

        Comment


          #5
          Re: Wonderful .. Data from kids into comma delimited string and stuffed into parent t

          yep - I figured as much - that the transition for you to xBasic is less of a hurdle than it is for me....

          the other reason I like to do 'stuff' in sql, via stored procedures or views - is that I can then access the data from my Report Builder, or from A5, or any other auxilliary app I may need - or even just have the answer in SQL and dump it into Excel....

          ie, I create summaries and calculations at the source, and then use it as needed

          I do the same 'philosophy' with my reports - I do maximum calculations and 'work' via SQL, and just use the Report Builder to 'paint the picture'

          I'm not saying I'm leaving A5 (in fact, I just committed). But, if I were to change to another platform, my formulas and summaries would not need to be re-created.
          MSQL since 2010
          A5V11 since Feb 2012

          Comment

          Working...
          X