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

Manually doing a lookup and populating fields.

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

    Manually doing a lookup and populating fields.

    Hello all,

    The current version of a data entry App uses the customer code (a 6 letter string) as the PK of the Customer table. The Invoice table's customer id field uses a lookup based on that string, so that when users are entering new invoices they type in the customer code and press tab, after which relevant fields from the customer record are copied to the invoice record.

    The app is being ported to SQL backend, where for reasons of efficiency the link between Invoices and Customers is an integer instead of a string. I successfully added a lookup to the Invoices table/customerid field to get the relevant information to the invoice record from the Customers' table, so that during data entry users can either enter the (integer) customer id or do a lookup for the customer if the id is unknown.

    To minimize the transition between the two version of the App, I would like to add a way for users to enter the customer code (string) on the Invoices form and have the relevant data pulled from the Customers table, just like it is done by the lookup.

    I am not sure how to do that in Alpha. The farthest I got was adding an unbound field to a form backed by a variable. I added an OnChange event handler that read in the customer code contained in the variable, and then queried the Customer's table for the records whose customer codes are like the value that was entered in the field (the full code is below).

    However, the next step would be to display a window that would allow the user to select which customer they want, and then populate the invoice's record with the relevant data.

    Is it possible to do that in Alpha? If so, how? Is there a better alternative?

    Any help is appreciated.

    Thank you,

    Armando

    Code:
    'Opens the default Form or Browse layout, displaying all, or selected records in the layout.
    'Check to see if you are running the script from within a Form
    
    dim flag_error as l
    flag_error = .f.
    if is_object(topparent.this) then 
    	p = topparent.this
    	
    	if eval_valid("P:Customerlookuptext.value") then 
    		DELETE Parameter1 
    		'Set the Parameter variable to the object's .value property
    		Parameter1 = eval("P:Customerlookuptext.value")
    	else
    		flag_error = .t.
    	end if 
    else
    	flag_error = .t.
    end if 
    
    if flag_error then 
    	ui_msg_box("Error","Customerlookuptext does not exist. This script cannot be run in this context.",UI_STOP_SYMBOL)
    	end 
    end if 
    
    filter = "[varC->parameter1] $ CUSTOMERDISPLAYNAME"
    Dim filter2 as C = replace_parameters(filter,local_variables())
    ui_msg_box("Filter2", filter2)
    
    query.filter = filter2
    query.order = ""
    
    'Open the default Form showing just the records that satisfy the filter
    DIM Shared varP_layout as P
    DIM enable_show_all as l 
    'The enable_show_all flag turns makes the Show-All button on the form toolbar gray.
    'This means that the user cannot turn off the base query for the form.
    enable_show_all = .f.   
    varP_layout =  a5_open_default_Form("customers",query.filter,query.order,"Temporary Query","",enable_show_all)
Working...
X