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

Using a script variable in a field rule...

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

    #16
    Re: Using a script variable in a field rule...

    Hi Stan-
    Thank you-

    I have established an interim table with the all the fields I need and posted them to my form, however, each session that is run will only summarize the columns that was entered for that day and when I open my form, I will come across 'ERROR' in some of the fields. How can I use Action Scripting, User Defined Functions, or XBasic to first checks for the existance of my field, and if it exists, returns the value, otherwise it could return "" or nothing?

    Thanks -

    Neecy

    Comment


      #17
      Re: Using a script variable in a field rule...

      Originally posted by neecy View Post
      first checks for the existance of my field, and if it exists, returns the value, otherwise it could return "" or nothing?
      That's not the way it works.

      It seems that you will need a "final" table with all of the possible fields. After your summary operation, append the existing fields in the summary table to the final table.

      A form built on the final table will not have errors for the unfilled fields.

      Since we know that all fields will exist in the final table we just need to find out what fields are in the summary table to build the append. To illustarate the principle I created a duplicate of the customer table (dup) in AlphaSports. I then built an append script which checks the fields in the customer table and appends existing fields to "dup".

      Code:
      tbl = table.open("customer")
      flds = tbl.fields_get()
      mlist = ""
      FOR i = 1 TO flds
      	fname = tbl.field_get(i).name_get()
      	mlist = mlist + if(len(mlist)>0,",","")+fname
      NEXT i
      tbl.close()
      
      uflds = w_count(mlist)
      '---
      a_tbl = table.open("dup")
      append.t_db = "customer"
      append.m_key = ""
      append.t_key = ""
      append.m_filter = ""
      append.t_filter = ""
      append.type = "All"
      append.m_count = uflds
      af = "append.m_field"
      ae = "append.m_exp"
      for x =  1 to uflds
      	afld = af+alltrim(str(x))
      	aexp = quote(word(mlist,x))
      	evaluate_template(afld+"="+aexp)
      	aexpv = ae+alltrim(str(x))
      	evaluate_template(aexpv+"="+quote("@customer->"+unquote(aexp)))
      next x
      append.t_count = 0
      a_tbl.append()
      There can be only one.

      Comment


        #18
        Re: Using a script variable in a field rule...

        Hi Stan-

        Thank you so much!!! :)

        That worked perfectly!!! :)

        Neecy

        Comment


          #19
          Re: Using a script variable in a field rule...

          Hi Stan-

          One last question. Is there anyway I can modify the current script to when if I specify my append.type = "Unique, replace existing", and my master table fields will replace if different from my transaction table. I want my case definition to equal "EITHER". The transaction table should replace current records in which there has be an update in the master or append if there is a new record added.

          Thanks-

          Comment


            #20
            Re: Using a script variable in a field rule...

            Try this.

            Code:
            tbl = table.open("customer")
            flds = tbl.fields_get()
            mlist = ""
            FOR i = 1 TO flds
            	fname = tbl.field_get(i).name_get()
            	mlist = mlist + if(len(mlist)>0,",","")+fname
            NEXT i
            tbl.close()
            
            uflds = w_count(mlist)
            '---
            a_tbl = table.open("dup")
            append.t_db = "customer"
            append.m_key = ""
            append.t_key = ""
            append.m_filter = ""
            append.t_filter = ""
            append.type = "Unique, replace existing"
            append.m_count = uflds
            af = "append.m_field"
            ae = "append.m_exp"
            [COLOR="Red"]ac = "append.m_case"[/COLOR]
            for x =  1 to uflds
            	afld = af+alltrim(str(x))
            	aexp = quote(word(mlist,x))
            	evaluate_template(afld+"="+aexp)
            	aexpv = ae+alltrim(str(x))
            	evaluate_template(aexpv+"="+quote("@customer->"+unquote(aexp)))
            	[COLOR="red"]aecase = ac+alltrim(str(i))
            	evaluate_template(aecase +"="+ quote("Either"))[/COLOR]
            next x
            append.t_count = 0
            a_tbl.append()
            There can be only one.

            Comment


              #21
              Re: Using a script variable in a field rule...

              Hi Stan-
              I received an error at a_tbl.append(). I am attaching my code to see what is wrong.

              Thanks-

              Neecy

              Comment


                #22
                Re: Using a script variable in a field rule...

                Yeah, that's why I said try....

                I get glassy eyed when I try to figure these out.

                Now try substituting this.

                evaluate_template(aecase +"="+"Either")

                for

                evaluate_template(aecase +"="+ quote("Either"))
                There can be only one.

                Comment


                  #23
                  Re: Using a script variable in a field rule...

                  Hi Stan-

                  Sorry, still didn't work. Same error at a_tbl.append()

                  Comment


                    #24
                    Re: Using a script variable in a field rule...

                    I'm not sure what you're paying me is worth all this time.

                    Code:
                    tbl = table.open("customer")
                    flds = tbl.fields_get()
                    mlist = ""
                    FOR i = 1 TO flds
                    	fname = tbl.field_get(i).name_get()
                    	mlist = mlist + if(len(mlist)>0,",","")+fname
                    NEXT i
                    tbl.close()
                    
                    uflds = w_count(mlist)
                    '---
                    a_tbl = table.open("dup")
                    append.t_db = "customer"
                    [COLOR="red"]append.m_key = "customer_id"
                    append.t_key = "customer_id"[/COLOR]
                    append.m_filter = ""
                    append.t_filter = ""
                    append.type = "Unique, replace existing"
                    append.m_count = uflds
                    af = "append.m_field"
                    ae = "append.m_exp"
                    ac = "append.m_case"
                    for x =  1 to uflds
                    	afld = af+alltrim(str(x))
                    	aexp = quote(word(mlist,x))
                    	evaluate_template(afld+"="+aexp)
                    	aexpv = ae+alltrim(str(x))
                    	evaluate_template(aexpv+"="+quote("@customer->"+unquote(aexp)))
                    	[COLOR="red"]aecase = ac+alltrim(str([COLOR="Green"]x[/COLOR])) [COLOR="Blue"]'change loop variable to match this example[/COLOR]
                    	evaluate_template(aecase +"="+ quote("Either"))[/COLOR][COLOR="Blue"]'put quote back in[/COLOR]
                    next x
                    append.t_count = 0
                    a_tbl.append()
                    There can be only one.

                    Comment


                      #25
                      Re: Using a script variable in a field rule...

                      Hi Stan-

                      I don't know what happened, but it worked. I copied the code and made changes to the file name yesterday and it didn't work. Today, it worked. :)

                      Thank you for you assistance. :)

                      Comment


                        #26
                        Re: Using a script variable in a field rule...

                        Sometimes the humidity level can mess things up.
                        There can be only one.

                        Comment

                        Working...
                        X