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

xdialog - one works, the other don't

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

  • #16
    Re: xdialog - one works, the other don't

    Originally posted by Stan Mathews View Post
    So you're saying the killfocus event is a killjoy?
    I've called it a variety of things including a kill joy. But we'll leave it at that.
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


    • #17
      Re: xdialog - one works, the other don't

      Thanks Stan & Al.

      Yeah, that was the problem. I had

      Code:
      If a_dlg_button = "empSelect_change"  	
      	getEmployee()
      			
      	a_dlg_button = ""
      End if
      in the code section. It didn't occur to me that other events might fire.

      This fixes it, of course:
      Code:
      If left(a_dlg_button,10) = "empSelect_"
      	If a_dlg_button = "empSelect_change"
      		getEmployee()
      	End if
      	
      	a_dlg_button = ""
      End if
      Peter
      AlphaBase Solutions, LLC

      Peter@AlphaBaseSolutions.com
      https://www.alphabasesolutions.com


      Comment


      • #18
        Re: xdialog - one works, the other don't

        Peter following this thread with interest (not that I understand much of the esoteric combinations of this dlg code) I call my dlg coding "poke around and try again"
        I have spent almost as many days on a multi data list dialog to improve the user data capture speed and experience (seconds) as I followed you work on your time machine.
        Yesterday I delivered a revolutionised (well I think so) status logging method that is now tight, compact and comprehensive with mm of mouse movement.
        1. the users hardly notice as they shoot through many more captures per minute without mistakes than with their previous system
        2. the more time you spend and the smoother it operates the less it is appreciated
        3. you will likely not be charging for the additional days spent beyond just having it work (For that simple thing? whats the big deal)

        Is it martyrdom? no definitely not, purism, perfectionism and dedication ? a fair amount, accolades? very little
        Satisfaction !!!
        Keep these coming it's just flippin' inspirational.

        I tell clients its easy to write a complicated application much harder to make it simple
        I will change my byline when I get the chance

        Comment


        • #19
          Re: xdialog - one works, the other don't

          Peter,

          From your first event case;

          The event name ( Red color ) should not using the Reserved names, -- See Event Syntax for Reserved name.


          If a_dlg_button = "empSelect_change"
          getEmployee()

          a_dlg_button = ""
          End if
          This is working for me
          Code:
           If a_dlg_button = "empSelect_change[COLOR="#FF0000"][SIZE=5]d[/SIZE][/COLOR]"  	
          	getEmployee()
          			
          	a_dlg_button = ""
          End if

          Comment


          • #20
            Re: xdialog - one works, the other don't

            Thanks John. Glad you pointed that out. Actually I already changed that one on general principles, but I have another one I'll have to check.
            Peter
            AlphaBase Solutions, LLC

            Peter@AlphaBaseSolutions.com
            https://www.alphabasesolutions.com


            Comment


            • #21
              Re: xdialog - one works, the other don't

              if I can add one more thing to posterity of this thread.

              use either debug(1) or write to the trace window to follow exactly what is happening - rather than what you expect to happen.

              Within a killfocus, only write the trace window since calling debug(1) will call the killfocus again and you'll get caught in loopy land.
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.
              "Make it as simple as possible, but not simpler."
              Albert Einstein

              http://www.iadn.com/images/media/iadn_member.png

              Comment


              • #22
                Re: xdialog - one works, the other don't

                Originally posted by johnkoh View Post
                Peter,

                From your first event case;

                The event name ( Red color ) should not using the Reserved names, -- See Event Syntax for Reserved name.




                This is working for me
                Code:
                 If a_dlg_button = "empSelect_change[COLOR="#FF0000"][SIZE=5]d[/SIZE][/COLOR]"  	
                	getEmployee()
                			
                	a_dlg_button = ""
                End if
                John/Peter/Al:
                Posterity bound:
                change is also an xdlg event.
                Change and changed are both legitimate xdlg events. The difference is when each fires.

                Comment


                • #23
                  Re: xdialog - one works, the other don't

                  G,

                  I agreed with you and this

                  The event name ( Red color ) should not using the Reserved names, -- See Event Syntax for Reserved name.
                  is wrong statement.

                  Thank you.

                  Comment

                  Working...
                  X