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



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

Stop help menu from working in report

  • Filter
  • Time
  • Show
Clear All
new posts

    Stop help menu from working in report

    Is there anyway I can stop the help menu (content) from working in the report preview/print. I have the sys menu hid in everything except the report. Can I delete some help file from the directory to keep it from pulling up.
    Also is there some way to prevent the about Alpha5 from working .
    Any help would be appreciated.

    RE: Stop help menu from working in report


    Rename the a_user.hlp file in the A5 program directory to something else, like a_user.old. This will keep the help from opening. What I like to do is build a simple help file with minimal help and name it a_user.hlp and rename the original. Then the user will get the help file I designed.



      RE: Stop help menu from working in report

      Thanks, I thought there may have been a file to change.

      I'll try it.


        RE: Stop help menu from working in report

        How do I make a help file to replace the original one?


          RE: Stop help menu from working in report

          There are any number of help authoring programs from very simple to very professional programs like Robohelp, which is quite expensive. I use Help and Manual 3, which is not real cheap, but is very good. Check 0ut



            RE: Stop help menu from working in report


            If the 'fit and finish' of a polished help system isn't critical, you could:

            1) put a button on your form,
            2) label it 'help'
            3) use it's OnPush event to run a script that pops up another form.
            4) on the called form have a large RTF field with text furnishing help info to the user

            This is a simple way to furnish context sensitive help, form by form in your app.

            You can also build a custom menu, with a Help topic. The submenu items could open other forms or PDF files for the user to peruse.

            Lots of options.

            -- tom


              RE: Stop help menu from working in report

              I don't have a problem with the forms, just the report menu. I have a5v4.03. I cannot disable the sysmenu in report preview and print. The custom menu doesn't work in report. I think the only solution is to make a new help file and replace the file.

              any more suggestions?


                RE: Stop help menu from working in report


                One of the big complaints in A5V4 was that you could have custom menus for nearly everything except print preview as it used the system menu. The only solution I found to the help problem was to rename the help file. A better solution is to update to A5V5 that allows customizing all menus as well as many other inprovements.

                Another issue is that users could close the whole application from this menu, which created some big problems if you had code that had to run on shutdown. There is a workaround, but it is a little messy and involves leaving a menu form open all of the time and trapping the CanExit event on that form.