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

Change table element from report

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

  • Change table element from report

    I have been trying to change a field from within a report and this is the second time I have tried to ask how to do it. The report is based upon a set which has a parent and two children tables. I compute a "balance due" from other fields in the report and wish to open one of the tables in this set, replace a value in this table (opening balance) so that the next time this report is run, the opening balance amount will be used to compute the new balance due field (which will again be saved to the table). I remember years ago having to open write and then close the table to do something like this. Does Alpha have an equivalent way to do this. I intend to use code attached to a button on the table which will Print the report. I will use the on push action of this button to store and run the code. Thanks for any help.

  • #2
    Re: Change table element from report

    You still have to open change and lose the table and can use a button on a form if you wish or do it with xbasic. I believe(not in alpha at the moment) you have a way to do it on after report is run using a script. Willl look when I get back to aa developer to verify I am right. Note: I never had to use it.
    Dave Mason
    dave@aldadesktop.com
    Skype is dave.mason46

    Comment


    • #3
      Re: Change table element from report

      In your report design use the primary key to create a hyperlink in the report to open a form to the record in the table you want to change; make the change, save and close the form.

      Create another form using a report preview supercontrol to display the report. Add a button to that form above the supercontrol that will refresh the report.
      topparent:xdialog1.refresh()

      When you call the report, open the supercontrol form.
      Last edited by MoGrace; 08-02-2019, 11:34 AM.
      Robin

      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

      Comment


      • #4
        Re: Change table element from report

        I had hoped to have this done automatically as there are nearly 200 different reports for different people to be generated each time. So opening a hyperlink and manually making a change for each of them would not be acceptable. I was looking for code that would automatically open, write, and close the table for each instance of the generated report. Is this not possible?

        Comment


        • #5
          Re: Change table element from report

          Without more info on the set structure, you leave us only guessing how to help.
          Robin

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

          Comment


          • #6
            Re: Change table element from report

            Sorry, thought I had mentioned the set. Parent _ Patients
            Transactions One to many with Patients
            \=Services One to one with Transactions (One service for each Transaction)

            Indexed on Patient ID

            Comment


            • #7
              Re: Change table element from report

              Hope you can see the organization. The board here did not keep my message as it was displayed when I wrote it.

              Comment


              • #8
                Re: Change table element from report

                Should have mentioned that the parent table has the field that I want to update. The field is named "balance due".

                Comment


                • #9
                  Re: Change table element from report

                  Just inadvertently unsubscribed to this thread by clicking the wrong reply in the email. How do I resubscribe?

                  Comment


                  • #10
                    Re: Change table element from report

                    David,

                    I would update the "Balance Due" field only after the user approves the printed report(s). The update would be done automatically using a script that replicates the calcs in the report(s).

                    I've found overwriting the "balance due" field problematic in my own work. You lose the transaction history and have no easy way to verify the balance due is correct. You might want to create patient_register to record each billable transaction, including date of the report (invoice?), opening balance, new charges or credits, and ending balance (an invoice number if applicable). Transactions in the register would be entered after the user approves the printed reports.

                    Comment


                    • #11
                      Re: Change table element from report

                      Tom I have been warned by my partner to do exactly as you suggest. A script sounds the way to do this. Thanks for the warning.

                      Comment


                      • #12
                        Re: Change table element from report

                        I have thought about what you said this morning and realize that we already have a "history" of all transactions (what you call the patient_register) in our table "transactions" which is a day by day history of all transactions sorted by patient number. So, how could I go about actually writing a script to change the balance_due field in the patients table. I tried creating a new script which could change records and it only takes me to a form of the patients table. I am just not sure how to go about this. Any help would be greatly appreciated. Thanks again for your reply.

                        Comment


                        • #13
                          Re: Change table element from report

                          Is the balance due field only related to a single patient? Ie, one record in the table per patient?
                          Robin

                          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                          Comment


                          • #14
                            Re: Change table element from report

                            David,

                            One way to get started is to think about how you'd do it with paper and pencil. Then think about which commands or functions are available in alpha to perform each step.

                            Doing this one step at a time might look like this:

                            - open the patients table and get the balance_due figure
                            - open the transaction table
                            - filter to show only tnx (transactions) for the current patient
                            - sum all the transaction charges one at a time by fetching through all tnx for that patient
                            - on each fetch add the tnx charge to a running total
                            - open the payments table
                            - filter to show only payments for the current patient
                            - sum all the payments for the current patient by fetching through all payments for the patient
                            - on each fetch add the payment amt to a running total
                            - subtract total payments from total charges
                            - this should be your patient's current balance
                            - change the balance_due in the patients table by replacing the old balance_due field value with the new one
                            - commit the change to disk
                            - close all opened tables

                            This approach computes the new balance by stepping through all transactions and payments for the patient. It does not try to compute new charges and new payments and use them to adjust the previous balance due figure.

                            there are summary operations available in Alpha that could simplify this, but if you're learning xbasic scripting doing it step by step will serve you well.

                            Comment


                            • #15
                              Re: Change table element from report

                              Yes

                              Comment

                              Working...
                              X