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


  • Filter
  • Time
  • Show
Clear All
new posts

  • StatusBar

    Using the following post as an example:

    Any chance of adding or replacing the "Please Wait" with a "Wait Dialog" with a progress bar. I have created a script that sends a table without confirmation and the table is quite large and takes 20-30 seconds to send. The function that Tom has shown does display a "Please Wait" but I'm looking to put in a dialog box with a "repeating" or "bouncing" progress indicator that will display when user send table and closes when table has been sent. Similar to what Tom's "Please Wait" does just with a progress indicator. Thank you in advance for your help...

  • #2
    Re: StatusBar

    If the waitdialog doesn't work (which it doesn't according to the other thread), why not just put a message in the PleaseWait dialog that tells the user that it might take a minute or two to complete. You could even change the font in the PleaseWait to a larger font so it can't be missed by all those lazy users who can't be bothered to read warnings. Unfortunately, the current length calculation doesn't work correctly for larger fonts so I modified it so that it will display correctly with any size font and as much text as you want (up to the 1024 character limit that A5 can work with in this case).


    1. I used stritran() to convert [[text1]] to whatever is in the text1 variable. The only "magic" to using the double brackets is (a) its uniqueness so I don't have to worry about accidentally changing something else that just happened to have the same character string in it and (b) in what it looks like if you forget to run the stritran() command to convert it - it looks like a really messed up field object which makes it very hard to miss when editing. This isn't a big deal on a small dialog like this one but I've been known to forget something in a large, complicated xdialog and didn't catch it until the customer saw it. Now I use the double brackets so it's really obvious if I forget something during development. (One of my more complex xdialogs has 30 stritran commands related to it - easy to miss one during initial development.)

    2. I added the {wrap=} command so a long text string would word wrap rather than running off the screen.

    3. I also removed the box_code since it wasn't serving any purpose in this particular script.

    FUNCTION PleaseWait as C ( Show = .F., what = "" )
    	'DESCRIPTION: This function displays a 'Please Wait' dialog for use while processing.	
    	'What is an optional parameter that will be displayed along with the words "Please Wait"
    	PleaseWait = ""
    	IF show = .F.
    		IF ui_modeless_dlg_exist( "Processing" )
    			ui_modeless_dlg_close( "Processing" )
    		END IF
    	END IF
    	text1 = what + " Please Wait"
    	box_code = <<%dlg%
    	{background=Pale Yellow}{wrap=120}
    	box_code = stritran( box_code, "[[text1]]", text1 )
    	ui_modeless_dlg_box( "Processing", box_code )
    	ui_dlg_move( "Processing", 2, 2.5 )
    	ui_modeless_dlg_setfocus( "Processing" )
    	ui_modeless_dlg_refresh( "Processing" )
    Last edited by CALocklin; 04-18-2012, 04:06 PM.