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

Multistate Button Report Selection Form

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

  • Multistate Button Report Selection Form

    As promised (but delayed by heavy schedule), the attached zip file include a form which shows how to use multi-state buttons to select a report, start and end dates, type of report output, and additional data ranges (60/90 day). The button marked "create" has error trapping for missing values (client and report) as well as the WinFax DDE script previously posted.

    Most sections of the script are bypassed since there are now reports included in this example (faster download). The file contains 3 tables and a database with one form. The zip file is about 78 K and unzips to about 580 K.

    By using low and high colors, little "panel lights" show which report was selected by appearing to turn on lights (light/dark green). If a report doesn't require starting/ending clients and/or dates a text box is activated saying "doesn't apply" and the fields are marked with yellow lights.

    After selecting client, dates, if the starting values are greater than the ending values, the fields and lights turn red. The form turns red while the create script is running since (in a larger database such as ours) some reports can result in the "blue bar of death" and noone wants the user to just turn off their computer and possibly fry the database.

    We use a smiley face as an exit button (when you can leave the form and stop working you're happy...). The border of the button is turned red to show the user that he can't leave (button is disabled) - some people don't get the concept of the form turning red.

    The report choice multistate button sets a number of values (indexes, lights on/off) in a script. The hardest part of the report choice button was ordering the choices so that rows and columns could be used with the lights. (It would be a lot easier if you could highlight and move a row in the choices parameter.) You can also set the values for the multistate in the form's script where the client names (A through K, skipping I since it looks like a 1). That method makes it a lot easier to play with the button's choice positions.

    Wherever you see a group of buttons it is probably a multistate doing sopmething or other.

    Try to not go too crazy playing with this. It's not as hard as it looks. As with most programming concepts, play around with the little parts and then just stick them all together (and hope it still works).

    Enjoy.

  • #2
    RE: Multistate Button Report Selection Form

    Almost forgot. The user must notice if there are any red "lights" on the fields showing ranges selected. Those fields and lights will be green if they are OK, and red if the starting value is bigger than the ending value.

    Comment


    • #3
      RE: Multistate Button Report Selection Form

      Typo in the second paragraph. There are NO reports in the files zipped (sentence above reads "There are now reports"). Some day I'll proofread better.

      Comment

      Working...
      X