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 list vs. date field conflict

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

  • xdialog list vs. date field conflict

    I have an xdialog with a list (actually 2 lists) linked, similar to a set (this happens to be SQL).
    The problem is that the date field interferes with the fetch of the 2nd list - but only when I scroll through list 1 using the down/up arrows. It starts off good, but after a 3 or 4 down arrows, list 2 is from then on out of sync (by 1) w. the parent list. Clicking on a row in list 1 always fetches the correct records in list 2. If I remove the date field definition from the xdialog (and say, put in a text field instead), I can scroll using the arrow keys and it always syncs correctly. Some date field event is firing and somehow interfering w. the fetch in list 2.

    Here is the date field:
    Code:
    [%DATE;P=popup.calendar(dtoc(vDate));I=popup.calendar%.30vDate!vDate_*]
    Here is the date event (standard Alpha derived code):
    Code:
    If left(a_dlg_button,6) = "vDate_" then 
    	if a_dlg_button = "vDate_killfocus" then 
    		vDate = ctod(dtoc(vDate))
    	end if 
    
    
    	if a_dlg_button = "vDate_changing" then 
    		vDate = ctod(dtoc(vDate))
    	end if 
    
    
    	trace.WriteLn(a_dlg_button)
    
    
    	a_dlg_button = ""
    End if
    Here are the 2 lists:
    Code:
    [%dk%.70,50 index^"PartNum:15|Plan Id:15|Lot:15|Qty:15
    "vProd_trans_sum_List!vSelect_prod_trans_sum_List_*];
    
    [%dk%.125,20 index2^"PartNum:15|Plan Id:15|Lot:15|Plan Qty:20|Picked Qty:20|
    Prev Built Qty:25|Closed:15
    "vProd_plan_List!vSelect_Prod_plan_List_*];
    Here is the list 1 key event code:
    Code:
    If a_dlg_button = "vSelect_prod_trans_sum_List_change" 
    	vArrayId = pList.Array[index].PartNum
    	
    	'' Filter child table (Prod_plan) on PartNum
    	pList2.ChildValue = vArrayId
    
    
    	vList2 = getList_Prod_plan(pList2)
    
    
    	Dim vProd_plan_List[0] as C
    	vProd_plan_List.initialize(vList2)
    		
    	vSize2 = pList2.Array2.size()
    	
    	If vSize2 > 0
    		Dim index2 as N = 1
    		Dim vArrayId2 as C = pList2.Array2[index2].Prp_PartNum
    	End If
    	
    	a_dlg_button = ""
    End if
    Can anyone suggest how I can keep my date popup calendar and mitigate the incorrect fetch of list 2?

    Remember, changing the date field to a text input box eliminates the problem. The issue seems to be the vDate_ event.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com



  • #2
    Re: xdialog list vs. date field conflict

    That is not very helpful.
    The hierarchy of the events here seems to play a role.
    You need to post the actual xdlg.

    I see one event that could possibly be eliminated (depending on the rest of the script):

    if a_dlg_button = "vDate_changing" then
    vDate = ctod(dtoc(vDate))
    end if
    In fact, and without knowing the rest of the script, I'd just go ahead and remove that event.

    Comment


    • #3
      Re: xdialog list vs. date field conflict

      Actually I need to remove the date event in it's entirety and then it works.

      Thanks for your insight.

      Addendum:
      Removing the code you suggested and removing:

      a_dlg_button = ""

      works also.

      I'm running this as a modeless xdialog.
      Peter
      AlphaBase Solutions, LLC

      [email protected]
      https://www.alphabasesolutions.com


      Comment

      Working...
      X