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

$25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

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

    #16
    Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

    I haven't tested this, but assuming it works anything like your calendar component, I think you're the winner. :)

    Comment


      #17
      Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

      Just seeing this post for the first time and giggling. I am surprised that anyone responded after the first few insults. Great sport.
      I hope you get paid, Jim.
      Last edited by agillbb; 01-25-2013, 12:35 PM.

      Comment


        #18
        Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

        Jim's already setup to take PayPal payments so there shouldn't be any good reason why not...

        BTW Jim, this code is an incredible step up from mine and just might be integrated lots of places in my app. Thanks for sharing.

        Comment


          #19
          Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

          Better get permission from cuz if Lawrence pays $25 for it, does he have the rights to it?
          TYVM :) kenn

          Knowing what you can achieve will not become reality until you imagine and explore.

          Comment


            #20
            Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

            Originally posted by lsprowls View Post
            Mr. Cone and Mr. Jinx: Since you don't have the answer, stop wasting my time (and that of everybody who reads this thread) by posting. And don't reply.
            WOW. Read through this and could not believe the attitude. I guess since he is willing to pay for it that he thinks he can have an attitude towards people. I guess he does not realize that the next time he has a question that one of the people that he has pissed off may be the one with the answer.
            Jeff Ryder

            Comment


              #21
              Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

              So I still haven't tested this code but it looks good--Lawrence, did Jim get your $25?

              Comment


                #22
                Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

                Originally posted by christappan View Post
                So I still haven't tested this code but it looks good--Lawrence, did Jim get your $25?
                I haven't seen a payment yet from Lawrence, but for those of you who do appreciate the code here's an update that uses a much nicer A5 window instead of those pesky javascript alerts. It comes from my calendar application and was created by using A5's examples. The main advantages over using a js alert are the alert's appearance is browser dependent and can be blocked. This code uses the style of the component for the pop up window and won't trigger the popup blocker. If you study the code you'll see you can add more buttons, add functions to those buttons, or turn them off. Add animation, toolbar buttons, etc.

                Code:
                if e.rtc.a_fieldValidationErrors.size() > 0
                	dim js as c
                	dim errorcontrol as c
                	errorcontrol = upper(e.rtc.a_fieldValidationErrors[1].varName)
                	js = <<%txt%
                					var pagename = "none";
                					var windowtitle = "Validation Error"
                					var windowid = '_valerror'; 
                					var btns = {};
                					btns['items'] = [
                					{
                						html: '',
                						name: 'x',
                						action: '',
                						disabled: false,
                						show: false},
                					{
                						html: '',
                						name: 'y',
                						action: '',
                						disabled: false,
                						show: false},
                					{
                						html: '',
                						name: 'z',
                						action: '',
                						disabled: false,
                						show: false},
                					{
                						html: 'OK',
                						name: 'zz',
                						action: function(){
                							this.hide();
                							
                						},
                						disabled: false,
                						show: true}
                					];
                					//btns['style'] = 'display:none;'; //uncomment to hide buttons.
                					btns['style'] = '';
                					var popupparms = {
                						type: 'modal-resizable',
                						width: '',
                						height: '',
                						bct: 'blank',
                						dbtns: btns,
                	%txt%
                
                	js = js + crlf() + "pmsg: "+"'<p style=\"margin: 10px;\"> " + e.rtc.a_fieldValidationErrors[1].errorText +"</p>'" + crlf()
                
                	js = js + <<%txt%
                						
                					};
                					jqcalPopUpWindow(pagename, windowtitle, windowid, popupparms);
                
                	function jqcalPopUpWindow(pagename, windowtitle, windowid, popupparms)
                	{
                		window.jqcal_popupwin = A5.PageWindows.createWindow(windowid, popupparms.type,
                		{
                			height: popupparms.height,
                			width: popupparms.width,
                			title: {
                				html: windowtitle,
                				tools: {
                					//items: false //uncomment if you don't want an X for closing the window in the title.
                				},			
                				location: 'top'
                			},
                			disableMove: false,
                			theme: '{grid.style}',
                			body: {
                				content: {
                					type: popupparms.bct,
                					url: '__workingMessage.a5w',
                					elementId: '~'
                				},
                				style: ''
                			},
                			onHide: function ()
                			{
                				return;
                		
                			},
                			//animation: {
                			//	show: {
                			//		type: 'fade',
                			//		duration: 'slow'
                			//	},
                			//	hide: {
                			//		type: 'fade',
                			//		duration: 'slow'
                			//	}
                			//},
                			buttons: popupparms.dbtns //need to add comma here if using options below.
                			/*optional top bar, bottom bar, header and footer. Uncommnet to use if desired.
                				tbar: {
                					show: false,
                					html: 'Top Bar',
                					style: ''
                				},
                				bbar: {
                					show: false,
                					html: 'Bottom Bar',
                					style: ''
                				},
                				header: {
                					show: false,
                					html: 'Header',
                					style: ''
                				},
                				footer: {
                					show: false,
                					html: 'Footer',
                					style: ''
                				}
                			*/
                		});
                		if (pagename != 'none')
                		{
                			$(jqcal_popupwin.getWindowId('body')).src = '__workingMessage.a5w';
                			jqcal_popupwin.show();
                			$(jqcal_popupwin.getWindowId('body')).src = pagename;
                		}
                		else
                		{
                			var currWindow = A5.PageWindows.getWindow(windowid);
                			var windowDiv = currWindow.getWindowId('body');
                			var arrHTML = [];
                			arrHTML.push('<p> </p>');
                			arrHTML.push('<p><strong>');
                			arrHTML.push(popupparms.pmsg);
                			arrHTML.push('</strong></p>');
                			arrHTML.push('<p></p>');
                			var windowHTML = arrHTML.join('\n');
                			$(windowDiv).innerHTML = windowHTML;
                			//$(windowDiv).innerHTML = popupparms.pmsg;
                			currWindow.show();
                		}
                	}
                	
                	%txt%
                
                	dialogValidate.hasError = .t.
                	dialogValidate.errorText = "Form has Validation Errors"
                	e.javascript = "{dialog.Object}.setFocus('"+errorcontrol+"');" + crlf() + js
                	
                end if
                Jim Coltz
                Alpha Custom Database Solutions, LLC
                A5CustomSolutions.com
                [email protected]

                Comment


                  #23
                  Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

                  Pretty COOL, Jim,

                  I think that should be worth 5-10 times more than the $25 in that you went above and beyond the advertised specs.
                  Last edited by forskare; 01-29-2013, 11:36 AM.
                  TYVM :) kenn

                  Knowing what you can achieve will not become reality until you imagine and explore.

                  Comment


                    #24
                    Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

                    Great solutions Jim and Chris, thank you for sharing.

                    Comment


                      #25
                      Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

                      Wow, this is gold! I'd been struggling to get enhanced validation notifications for a while. I haven't tried the code yet, but I have it saved. If it doesn't work, you can send $25 to my paypal account for wasting my time, heh. Seriously though, thank you guys.

                      Comment


                        #26
                        Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

                        Originally posted by totallycovered View Post
                        Wow, this is gold! .......... If it doesn't work, you can send $25 to my paypal account for wasting my time, heh.
                        Ahhh, but look at the fun you've had doing it. LL And to think it's all because Lawrence wanted/s to pay someone $25 to help him accomplish a task. Will we ever know if this met his criteria and if not, how short is it? Does it do some of what he wants or is the $25 a great bargain?

                        I don't have a use for it at this point but if someone does, let us know so Lawrence can be thanked for starting this thread even though he might think it is/was a waste of his time. So Lawrence, please realize that the requests and answers posted here benefit far more than the poster and/or the responder. Even though it may not help you, we do not believe it is/was a waste of your time.
                        TYVM :) kenn

                        Knowing what you can achieve will not become reality until you imagine and explore.

                        Comment


                          #27
                          Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

                          Response to #14:
                          a) If a record is saved quickly, the message displayed by the the onClick script flashes. Users may find this disconcerting as they will not have time to read the message.
                          b) The afterValidate script correctly displays a message if any field on the form contains an error, however the cursor remains at the bottom of the form so the user may not see the error(s). I modified the script to scroll the form to the top to force the user to scroll down through the form and see the errors.

                          Code:
                          if (e.hasErrors) {
                          	self.scrollTo(0,0);
                          	A5.msgBox.show('Erreur','<div style=\'padding: 20px;\'>Il y a une erreur sur le formulaire.</div>','o',function() {});
                          }
                          Response to #15:

                          The fields in the dialog are grouped into frames. On error, the window scrolls to unexpected positions. Examples:
                          • If the first frame contains errors, the window scrolls to that frame's last, not first, row of erroneous fields.
                          • If the fields in the last row of the first frame are valid but the second frame contains errors, the windows scrolls to the last row of the second frame even though higher rows in both frames one and two contain erroneous fields.
                          • Only when all other fields are valid, does the window scroll to the first field in the dialog when it contains errors.

                          Erroneous fields are often hidden from the user because they have scrolled off the screen.

                          Response to #22:
                          Same as #15.

                          Comment


                            #28
                            Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

                            Did you pay Jim? Your original post allowed for "Acceptable" solutions, and his was far more than "Acceptable".

                            Otherwise, you've only been rude and now that you've finally responded weeks later to one "Acceptable" solution and one far-better-than-"Accpetable"-even-if-it-remains-below-your-perfect-standards solution (while your pre-"Acceptable" solutions were given negative responses within hours), you still only offered criticism without any appreciation for anyone's effort.

                            I wish you the best. If you haven't paid Jim, you've proven yourself a liar on top of rudeness; regardless, no one wants to hear you complain anymore.

                            Comment


                              #29
                              Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

                              Originally posted by lsprowls View Post
                              Response to #14:
                              a) If a record is saved quickly, the message displayed by the the onClick script flashes. Users may find this disconcerting as they will not have time to read the message.
                              b) The afterValidate script correctly displays a message if any field on the form contains an error, however the cursor remains at the bottom of the form so the user may not see the error(s). I modified the script to scroll the form to the top to force the user to scroll down through the form and see the errors.

                              Code:
                              if (e.hasErrors) {
                              	self.scrollTo(0,0);
                              	A5.msgBox.show('Erreur','<div style=\'padding: 20px;\'>Il y a une erreur sur le formulaire.</div>','o',function() {});
                              }
                              Response to #15:

                              The fields in the dialog are grouped into frames. On error, the window scrolls to unexpected positions. Examples:
                              • If the first frame contains errors, the window scrolls to that frame's last, not first, row of erroneous fields.
                              • If the fields in the last row of the first frame are valid but the second frame contains errors, the windows scrolls to the last row of the second frame even though higher rows in both frames one and two contain erroneous fields.
                              • Only when all other fields are valid, does the window scroll to the first field in the dialog when it contains errors.

                              Erroneous fields are often hidden from the user because they have scrolled off the screen.

                              Response to #22:
                              Same as #15.
                              Lawrence,

                              Perhaps you could post an example zip file so we could see what it's doing. That would be fair, would it not?
                              TYVM :) kenn

                              Knowing what you can achieve will not become reality until you imagine and explore.

                              Comment


                                #30
                                Re: $25 for the Best Answer for Active Display of Dialog Field Validation Errors!!

                                I don't have the answer but this thread is very entertaining .... subscribed!

                                -Mike
                                Mike Brown - Contact Me
                                Programmatic Technologies, LLC
                                Programmatic-Technologies.com
                                Independent Developer & Consultant​​

                                Comment

                                Working...
                                X