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

Reports Only Print when all menus closed

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

  • Reports Only Print when all menus closed

    Some of my reports that have "onrecord" append and update operations only work correctly when all menus are closed and the report is executed from the control panel. Anybody know what the cause and solution is for this.

  • #2
    Re: Reports Only Print when all menus closed

    reports that have "onrecord" append and update operations
    I've no experience with this. Will you elaborate?
    There can be only one.

    Comment


    • #3
      Re: Reports Only Print when all menus closed

      Hi Stan,

      I have created a system that automates the sending of parking violation letters for an HOA. I used the Create Report option to design my letter so that it would be easier to reference the actual violations.

      If you right click on a report, select Design. At the top of the screen you have a Report drop-down. I go to Section Events. My report has a section called prop_street_addr. Each change in property street address triggers a new letter. On this section event you can define onrecord events. When I am on the record I do an append operation to a letter history table that records the date the letter was sent, the type of infraction, and the letter level they were on when the letter printed (Courtesy, Violation, Final Notice, Call to Hearing).

      I also do a second update event that increments the letter level by 1.

      If I run this report print operation from the menus the update operation fails telling me that the table to be updated (owners) is already in use. I have to close all menus and run from the control panel, then I don't get an error. Hope that detail helps.

      Comment


      • #4
        Re: Reports Only Print when all menus closed

        Clearer even though I'm not certain what

        run this report print operation from the menus
        means.

        Do you have a menu form? If so, on what table is the menu form based. Most would create a "dummy" table used for nothing other than creating forms to hold such menus/buttons. In this way the table needed for the operation (append, update) is not being used by the form.

        Since you can run your report from the control panel, I assume this is the issue. I have never run a saved operation from the report events. While it is working for you, the more common approach would be to script the entry of the new record in the history table and script the changing of the letter level. Those scripts shouldn't run in to the usage conflict.

        If you want some help with that approach, let me know.
        There can be only one.

        Comment


        • #5
          Re: Reports Only Print when all menus closed

          I do indeed have a menu form.

          You solved my problem for me.

          It never occurred to me to have all my menu forms run against a "dummy" table. I created a single field dummy table with zero records and copied my menu forms to it. Problem solved.

          Right now I still do everything with action scripting. I know that I will be able to tap into a lot more power using xbasic, but my focus for the businesses I'm supporting is to get the data out of 1000's of excel spreadsheets, each with 60 tabs and into a real relational database.

          Comment

          Working...
          X