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

Nagging Empty Expression

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

    Nagging Empty Expression

    I have a table (see attached screenshot) which has the following fields
    ClientID
    Date
    SessionCode
    SessionFee
    Payment
    PayType.

    The ClientID and sessionCode have table lookups that work fine.

    The Session fee has a table lookup that his based on the SessionCode, the lookup works and returns the correct value, but when you exit the field you get an error of "empty expression". If I remove the lookup for SessionFee then no error. I've played around with the lookup syntax but can't get rid of the error.

    IF the attachements worked you will find a screenshot of the error and a screenshot of the field rules for the table lookup.

    Any direction or help is appreciated.

    Thanks
    tom

    #2
    Re: Nagging Empty Expression

    Your screenshot doesn't show the complete definition of the field rule lookup since we can't scroll. Best attach a sample database.
    There can be only one.

    Comment


      #3
      Re: Nagging Empty Expression

      Stan

      Attached is a zip file of the database, no password needed. All of the data is scrambled to protect the innocent. You can just click on the sessionselectdata table in browse mode to see the issue. Also if you go into the field rules you will get an error as a global variable needs to be set through opening the main client form which is how you would normally get to this table. The overall process is to select clients seen that day from the main form which then starts a batch process (opens browse view on session select table) for entering session data.

      Thanks,
      Tom

      Comment


        #4
        Re: Nagging Empty Expression

        Seems to work fine here in the default browse. I'm using v8 instead of v9.
        There can be only one.

        Comment


          #5
          Re: Nagging Empty Expression

          Yes, it does work in Version 8. I even tried reinstalling Version 9, but the same problem. Is there anything you can recommend on the coding of the lookup that might mitigate the problem?

          thanks,
          Tom

          Comment


            #6
            Re: Nagging Empty Expression

            Since it works in v8 and not in v9 I'd recommend you report it. If this just happened after the latest patch, reapply the prior patch if you don;t need something it offered.
            There can be only one.

            Comment


              #7
              Re: Nagging Empty Expression

              I've also had this problem lately in v9. What seems to fix it for the time being is closing down and then getting back in a5. But then it might raise it's head again after doing some more work on the app and going back to the form I'm using that has the lookups causing the errors. So would be hard to duplicate the error as far as submitting a bug report.
              Ernie

              Comment

              Working...
              X