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

UX with many embedded grids

  • Filter
  • Time
  • Show
Clear All
new posts

  • UX with many embedded grids

    I have a ux with lots of embedded grids. Anyway to save all new data on the ux And embedded grids at the same time?

    Thanks for your help.
    Reed Brown
    ITOT Solutions, Inc.
    Alpha v12

  • #2
    Re: UX with many embedded grids

    If your UX allows record navigation then it seems to me it will be quite a mess to update the grids and then cancel the navigation if there is any type of error saving the grids.

    In my app I had one main grid and just two linked grids. One of the linked grids was updateable, the other was read-only. It was are too much effort trying to ensure the main grid told the child grid to update when the user navigated the main grid or otherwise did something requiring the data to be saved. The process was slow running and difficult to program. In the web browser you never know what sequence things will run in. So, there was all kinds of error checking I had to throw into the code. Eventually, I ripped out the two child grids and now call them as modal popups -- life is so much simpler now and people don't mind viewing or updating data in the popups instead of on the main grid.

    Perhaps I go overboard on error checking, but I believe all of the error checking you see in the following code was put their because it was an error condition that came up in trying to test and develop the code. The only purpose of the following function is to tell one linked grid to save its data: !!!

    function SaveLinkedGridComments()
       // ** Comments now in modal popup, not Linked Grid, so following is no longer used.
    	// See if linked grid exists yet, and if it is dirty then flush changes to disk	
    	var gr = {grid.object};
    	if(typeof gr != 'undefined') {
    		if( '_linkedGrids' in gr) {
    			if(gr._linkedGrids['LINKCMNT'] != undefined) {
    				if(gr._linkedGrids['LINKCMNT'][0] != undefined) {
    					var linkedCMNT = window[gr._linkedGrids['LINKCMNT'][0] + '_GridObj'];
    					if(linkedCMNT != undefined) {
    						var cmnt_dirty = false;
    						if('_isDirty' in linkedCMNT) {
    							if(linkedCMNT._isDirty) {
    								cmnt_dirty = true;
    							else {
    								cmnt_dirty = false;
    						else {
    							alert('Unexpected error: flag1 not found!');
    						var cmnt_dirty2 = false;
    						if('_getGridVariables' in linkedCMNT) {
    						    var linkedCMNTGrid = {};
    						    var linkedCMNTDtl = {};
    						    if(linkedCMNTGrid.isDirty) {
    						    	cmnt_dirty2 = true;
    						else {
    							alert('function _getGridVariables not found');
    						if( cmnt_dirty != cmnt_dirty2 ) {
    							alert('Unexpected error: Change detection flags not equal! Flag1 = ' + cmnt_dirty + '  Flag2 = ' + cmnt_dirty2 );
    						if( cmnt_dirty == true || cmnt_dirty2 == true ){
    					        linkedCMNT.submitGridPart(); // SUBMIT COMMENT DATA
    					else {
    						alert('Unexpected error: Linked Detail Grid not found for Comment Area!');
    				else {
    					alert('Unexpected error: Linked Comment Area Not Found!');
    			else {
    				alert('Unexpected error: Linked Section Not Found!');
    		else {
    			//--- Removed linked grids in favor of popups
    			// when grid first loads the linked grids have not been attached yet.
    	else {
    		alert('Unexpected error: grid object not defined - {grid.object} ');
    } // End SaveLinkedGridComments()
    Last edited by RichCPT; 12-09-2014, 09:53 PM. Reason: some typos corrected