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

New Grid Events

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

    New Grid Events

    Are there any tutorials at all for the Events section of grids so I can understand by seeing it in action? (ie: e.rv, e.rtc, pagevariables as p, e as p, etc.

    I'm really having problems understanding how i would incorporate info from my dialog into the grid events. For instance, I am using a lookup feature. It looks for the dealer in another table and updates name, address, city, state, zip, etc. If it doesn't find it, the user enters that info and when they press enter, the dealer table that was used for the lookup is updated. below is how i did the code in the dialog. There are several tables that would require the same thing.

    Code:
    ix  = tbl.query_create("N","Dealername = "+quote(alltrim(CurrentForm.Controls.Dealername.value)))
    recs = ix.records_get()
    
    if recs = 0 then
            tbl.enter_begin()
     	     	tbl.dealername =  alltrim(CurrentForm.Controls.dealername.value)
     	 		tbl.address =  alltrim(CurrentForm.Controls.Address.value)
    		 	tbl.Csz =  alltrim(CurrentForm.Controls.CSZ.value)
                tbl.phone =  alltrim(CurrentForm.Controls.phone.value)
                CurrentForm.Controls.dlrid = tbl.Dlrid
    		tbl.enter_end()
                
    	else 
    	 	        CurrentForm.Controls.dlrid = tbl.Dlrid
    				tbl.close()
    end if
    I'm working in the 'afterupdaterecords' for the above.
    Up and coming Alphaholic ;)

    #2
    Re: New Grid Events

    I really would like to get my head around the events section in a grid.

    Can someone please guide me in the right direction? Something that gives you some examples of how to use the events?
    Up and coming Alphaholic ;)

    Comment


      #3
      Re: New Grid Events

      Elena,

      I have not seen anything regarding grid event, other than the minimal help and comments that are in the event section of the grid.

      From what you describe above, it seems like this can all be done with no coding.

      Is you goal to add/edit/delete records from/to a dealer table?
      Bill Griffin
      Parkell, Inc

      Comment


        #4
        Re: New Grid Events

        Elena,

        Here is a link to a video which is pretty helpful with the new grid events

        Comment


          #5
          Re: New Grid Events

          From what you describe above, it seems like this can all be done with no coding.

          Is you goal to add/edit/delete records from/to a dealer table?
          That would be great without coding but the main table I'm using is called workorder.dbf and the lookup is coming from dealer.dbf.

          The goal is to do a table lookup and update workorder.dbf with Dealer name and dealer number. If that dealer does NOT exist in dealer.dbf, the person does the edit combo and enters all the pertinent info on the web form and then it would be added to the dealer table AFTER the submit button is pressed.

          That's why I'm thinking I need to do some programming in the 'afterupdaterecords' event.
          Up and coming Alphaholic ;)

          Comment


            #6
            Re: New Grid Events

            Sounds like you just need to make the dealer id a mandatory field.

            Then use a lookup (grid style) that is based on the dealers table and that allows adding new records.


            Job done - unless I am missing something which has been known to happen...

            Comment


              #7
              Re: New Grid Events

              I was trying to stay away from using another grid component for the lookup but i may have to if i can't figure out how to use the code i have in the events section.
              Up and coming Alphaholic ;)

              Comment


                #8
                Re: New Grid Events

                Hey there. I ran into some similar problems this evening while trying out v10 for the first time. I got it working by doing the following:

                In a Dialog component you used code in your after validate that looked something like:

                tbl.fieldname = alltrim(CurrentForm.Controls.fieldname.value)

                When using a grid in place of a dialog component you will want to structure your code a little differently. First off, there is no after validate. Your code goes in the "AfterInsertRecord" event. It would be structured like the following:

                tbl.fieldname = alltrim(e.DataSubmitted.fieldname)

                You basically use "e.datasubmitted" in place of "currentforms.controls" (without the ".value" on the end as well)

                session variables are also set a little differently here.

                Instead of:

                session.myvariable = "something"

                you would need to enter

                e.rv.session.myvariable = "something"


                Hopefully these small observations can help you on your road to figuring out the new event sections.

                Comment


                  #9
                  Re: New Grid Events

                  yes, you are correct that after validate event is replaced by after insert record event, but i have problem with report printing, usually i used after validate event on dialog component and i usually using Genies to create the code, below is one of my dialog after validate event that created by genies.
                  any idea, how to translate it if i use grid on after insert record event?

                  regards,
                  Andy


                  dim args as sql::arguments
                  dim dDRTGL as d
                  dim dSPTGL as d
                  dDRTGL=CurrentForm.Controls.DRTGL
                  dSPTGL=CurrentForm.Controls.SPTGL
                  args.set("ArgDRTGL",dDRTGL)
                  args.set("ArgSPTGL",dSPTGL)
                  dim filename as c
                  dim libfolder as c
                  libfolder = a5_removetrailingbackslash(Request.ApplicationRoot) + chr(92)
                  if Jenis="1" then
                  reportname = "Rpt_LISTPJLBYTGL@" + libfolder + "its.alb"
                  end if
                  if Jenis="2" then
                  reportname = "Rpt_LISTPJLBYTGLND@" + libfolder + "its.alb"
                  end if
                  filename = session.session_folder + "RptLISTPJL.pdf"
                  filename = report.saveas(reportname,"pdf","","",filename,.f.,null_value(),args)
                  if file.exists(filename)
                  currentform.RedirectTarget = session.session_url + "RptLISTPJL.pdf?" + time("hms3")
                  end if
                  skipreport:

                  Comment

                  Working...
                  X