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

Create lookup rule in Xbasic

  • Filter
  • Time
  • Show
Clear All
new posts

  • Create lookup rule in Xbasic

    Hello all,
    I'm working on a little project that requires addition of one extra filed to a few tables. Additionally, the new field needs a simple lookup definition. I would like to accomplish that in a XBasic to simplify the deployment.
    The only information I have found on this topic is here:
    Thanks to Stan Mathew's reply I was able to come up with this code:
    FUNCTION update_table AS C (tn as C, prefix as C )
    	on error goto error_handler
    	'create new columns
    	dim fields as C =''
    	 fields = prefix +"_tax_type,c,4"+crlf()			
    	 fields = fields+ prefix +"_tax_value,n,15,2"			
    	'set the lookup rule to tax_type
    	dim rul as P
    	dim t as P
    	dim fType as P
    	dim fGST as p
    	dim fValue as p
    	dim frul as P
    	t =
    	rul = t.rules_get()
        	eval( "rul." + prefix+"_tax_type.lookup.Type = "+s_quote("Table"))
    		eval( "rul." + prefix+"_tax_type.lookup.table_list.insert()")
    		eval( "rul." + prefix+"_tax_type.lookup.Table = "+s_quote("lookup_tax.dbf"))
    		eval( "rul." + prefix+" = "+s_quote("Id"))
    	temp = frul.table_list.[1]
    	temp.Condition = ""
    	temp.Display = "No"
    	temp.Fill = prefix +"_tax_type"
    	temp.Source = "Id"
    	temp.Width = 4
    	temp = frul.table_list.[2]
    	temp.Condition = ""
    	temp.Display = "Yes"
    	temp.Fill = ""
    	temp.Source = "Name"
    	temp.Width = 10
        err = error_code_get()
        msg = error_text_get(err)
        ui_msg_box("Error", msg)
    Unfortunately it doesn't work. I'm getting an error that the 'rul.column_name.lookup' property does not exist. However when I try this code in the interactive window I'm able to add the lookup rule successfully:
    t ='table_name')
    rul = t.rules_get()
     rul.col_name.lookup.Type = "Table"
     rul.col_name.lookup.Table ="My_Lookup_table"
     rul.col_name.lookup.Link "ID";
    rul.col_name.lookup.table_list.[1].Source = "Name"
    rul.col_name.lookup.table_list.[1].Display = "Yes"
    Can anybody explain why does it work in the interactive window, but doesn't inside the function? What is missing in that function to make it work?
    Any help is greatly appreciated!

  • #2
    Re: Create lookup rule in Xbasic

    It has been a whiile since I delved into this area. I see you dimmed frul as P and used that pointer in


    Where do you assign something to this pointer?
    There can be only one.


    • #3
      Re: Create lookup rule in Xbasic

      Thanks for the super fast reply! You are right - that might cause some problems down the line, but for now I'm not even getting that far. The code crashes on that line:
      eval( "rul." + prefix+"_tax_type.lookup.Table = "+s_quote("lookup_tax.dbf"))

      although this code runs successfully:
      eval( "rul." + prefix+"_tax_type.lookup.Type = "+s_quote("Table"))

      it seems like it has no effect on the table/filed.


      • #4
        Re: Create lookup rule in Xbasic

        Problem Solved!

        As I said in the post above, this line
        eval( "rul." + prefix+"_tax_type.lookup.Type = "+s_quote("Table"))
        seems to have no effect - well that is precisely what happens - the code above did not assign the value to the property, it basically evaluated the statement (is property equal to this value) and returned false! To work around this i had to do this
         temp = eval( "rul." + prefix+"_tax_type.lookup") 'this will return the pointer to lookup property
         temp.Type = "Table" 'this will assign the value to the property
        rest of the code needs adequate changes.

        I have enough of Alpha for one day, but if somebody is interested please post here and I can publish the final working version of my function!


        • #5
          Re: Create lookup rule in Xbasic

          Glad you found a solution. I think this would also work

          eval( "rul." + prefix+"_tax_type.lookup.Type") = "Table"


          evaluate_template( "rul." + prefix+"_tax_type.lookup.Type = "+s_quote("Table"))
          There can be only one.