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

Lookup problems

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

    Lookup problems

    I wish to set the default value for a field in sequence based on 2 fields: Year and Ref; e.g., 2011-236.
    I am using a standard grid in single record, form style, to input the records.
    I use the following to look up the next Refcount3 value for 2011:

    =cyear(Date())+"-"+convert_type(tablemax("C:\Installations.dbf","Year='2011'","Refcount3")+1, "c")

    which works fine though the year part is referenced directly. I would prefer the following format;

    =cyear(InstallDate)+"-"+convert_type(tablemax("C:\Installations.dbf","Year='cyear(InstallDate)'","Refcount3")+1, "c")

    Here the year is deduced from the install date as input by the user, could be any year. However this doesn't work. It's as if the lookup based on the input date just doesn't work. No errors, just returns nothing.
    Any ideas anyone?

    #2
    Re: Lookup problems

    I would say

    =cyear(InstallDate)+"-"+convert_type(tablemax("C:\Installations.dbf","Year='cyear(InstallDate)'","Refcount3")+1, "c")

    should be

    =cyear(InstallDate)+"-"+convert_type(tablemax("C:\Installations.dbf","Year = "+quote(cyear(InstallDate)),"Refcount3")+1, "c")
    There can be only one.

    Comment


      #3
      Re: Lookup problems

      =cyear(InstallDate)+"-"+convert_type(tablemax("C:\Installations.dbf","Year = "+quote(cyear(InstallDate)),"Refcount3")+1, "c")

      Thanks, but is the "+quote' string literal? Is that what you meant?

      Comment


        #4
        Re: Lookup problems

        Literally the expression suggested.

        Code:
        =cyear(InstallDate)+"-"+convert_type(tablemax("C:\Installations.dbf","Year = "+quote(cyear(InstallDate)),"Refcount3")+1, "c")
        You can copy and paste from here.

        The filter "Year='cyear(InstallDate)'" evaluates to Year = the text 'cyear(InstallDate)'

        The filter "Year = "+quote(cyear(InstallDate)) evaluates to Year = cyear(value_in_InstallDate_variable)
        There can be only one.

        Comment


          #5
          Re: Lookup problems

          Thanks Stan,

          this works perfectly in an ordinary desktop form, but not on a web form. On the desktop form i tried it as a calculated field, and as soon as the date field was filled the calculation evaluated correctly as expected.
          on the web form all i get is 'Initial Value Error: Variable "InstallDate" not found.' Though Installdate is the name of a field not a variable - syntax issue perhaps??
          if i use it in a calculated field within the web form/ grid, it evaluates correctly in the design section, but i cannot get it to appear on the live web form.
          How do you get a calculated field's value to show on your grid?

          Comment


            #6
            Re: Lookup problems

            I don't do grids/web. Just trying to help with the syntax. Seems there should be a way to pass the variable to the function.
            There can be only one.

            Comment


              #7
              Re: Lookup problems

              Having looked at this again, I have to assume that the reason the expression works in the desktop form and NOT in the web form is because the Installdate is instantly assigned to the installdate field when using the desktop form. However when using the web form the installdate value has only been assigned to the web interface - not to the actual table until the record is submitted. In this case, (if I'm correct??), the expression fails because it is being referred to a value that does not yet exist in the table. The solution would then be to have the installdate registered as a variable once input on the web form, then have the expression refer to that variable. Any idea how i might go about this?

              Comment

              Working...
              X