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

LOOKUPN help

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

    LOOKUPN help

    Hi,

    I having a terrible time getting this function to work. I cannot wait for V5 which I understand will make this much easier.

    I want to lookup in a database called TRIPS.DBF on the field TRIPS->Miles_IN, to find the Largest or Last number in this field and bring it back to a VEHICLE.dbf and fill in VEHICLE->ODOMETER field. ODOMETER is a calculated field and the following expression is the calculation.

    LOOKUPN("L",ODOMETER,"MILES_IN","TRIPS.DBF","MilesIn")

    MilesIn is an index based on Miles_In. I tried using "F" for first, but couldn't get it to work either. I do want the Last or Largest number so I thought "L" was appropriate.

    What am I doing wrong?

    TIA

    Tom

    #2
    RE: LOOKUPN help

    I don't think V5 is going to help you with this. The lookup functions return a value only when there is an exact match to the lookup value in the named table and index. If there is the possibility of more than one exact match, the F(irst), L(ast) and C(losest) determine which value is returned.

    It sounds to me like you might need to use dbmax or tablemax if you are looking for a largest value among groups. If all you need to know is the largest value in the milesin field in vehicle.dbf, an index on that field and a fetch_last would also do it.

    Finian Lennon
    Finian

    Comment


      #3
      RE: LOOKUPN help

      Finian,

      Thanks for responding to my message. (Since the conference, I am able to put a face to your name.)

      You have the right idea, "If all you need to know is the largest value in the milesin field in vehicle.dbf, an index on that field and a fetch_last would also do it."

      Could you suggest some code to get this trip.Miles_in.value and put it into Vehicle.odometer.value?

      Thanks

      Tom

      Comment


        #4
        RE: LOOKUPN help

        Hi Tom,

        F finds the 1st record with an exact key match
        L finds the last record with an exact key match
        C on the other hand finds a key that is equal to or greater than the key given.

        To get the maximum number, you must use a "C" with an index that is descending in value.

        LOOKUPN("C",INVERT(ODOMETER),"MILES_IN","TRIPS.DBF","MilesInDescending Index")

        You might find it easier to use an index expression that is character based, e.g.

        INVERT(STR(MILES_IN,10,0))

        and a key like

        INVERT(STR(ODOMETER,10,0))

        You may have to play with the key value (invert may not be needed there) to get the right expression, but it will work.

        Using DBMAX is absolutely the wrong way to do it as it must read every record that matches the key.

        Regards,

        Ira J. Perlow
        Computer Systems Design & Associates
        [email protected]
        Regards,

        Ira J. Perlow
        Computer Systems Design


        CSDA A5 Products
        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
        CSDA Barcode Functions

        CSDA Code Utility
        CSDA Screen Capture


        Comment


          #5
          RE: LOOKUPN help

          You might try another method for this. I'm do no think that not sure a field rule (for the vehicle table) is the answer. The thing that should kick off changing the odometer reading is the addition of an odometer reading for a trip. On the trip database you could have a posting field rule that posts the odometer reading from the trip back to the vehicle reading. Within the posting rule you might want a condition using the lookupn function backt to the vehicle that says "don't update this odometer reading to the vehicle if the odometer reading reading on the vehicle is greater than this particular trip reading".

          Good Luck

          Comment


            #6
            RE: LOOKUPN help

            Thanks to all - I got it!!!

            Lots of trial and error, but I got it!

            Thank you Ira, John, Finian, et al. What a great group.

            Tom

            Comment

            Working...
            X