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

A5 confusing a variable ref with a table handle...

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

    A5 confusing a variable ref with a table handle...

    I have a form that does some brutish calculations such that every time you move the record pointer there is a bunch of number crunching and it is a little distracting and poky. So I added a logical variable to the form and prefaced the calc fields with
    if(FLHCALC, crunch_crunch,0)
    I then set the variable to .F. and put a check box on the form. Lovely. FLHCALC = .F., we bip around merrily with no messy mathematizing. Click the checkbox and we get a whole other set of live analysis. Great stuff.

    Finally, as I like things colorful, I activated the checkboxes color equation and entered if(Var->Flhcalc,"Black on Yellow", "Black on Gray")

    On evaluating I get the error message "invalid table handle"

    Where does THIS come from?

    #2
    RE: A5 confusing a variable ref with a table handl

    Stephen: RE: Invalid Table Handle

    "...Where does this come from....?"

    I'll tell ya - OUT OF MY MACHINE! I've had the same, exact message for no apparent reason. I've seen it several times working against an if statement that otherwise should work.

    Let's call the ITH nemises! GEEZ -- I thought it was ME!

    Ken

    Comment


      #3
      RE: A5 confusing a variable ref with a table handl

      Wait.....

      I'll bet Tom Cone or Ira knows why!

      Ken

      Comment


        #4
        RE: A5 confusing a variable ref with a table handl

        Stephen,
        I'm not sure what this is, but you might try setting a second variable at the same time with the same true or false value as the first variable. Then use the second variable in the color equation.
        John

        Comment


          #5
          RE: A5 confusing a variable ref with a table handl

          Why would it not be:

          if(var->FLHCALC , crunch_crunch,0)

          or

          if(Flhcalc,"Black on Yellow", "Black on Gray")

          (without the Var->)

          but then the "threading" of the color equations seems to cause problems at times. Have you tried:

          if("expression defined for 'FHCALC'","Black on Yellow", "Black on Gray")
          There can be only one.

          Comment


            #6
            Looks like a bug...

            This error only occurs in the expression builder used to create a color equation, and occurs when you try to evaluate ANY variable.

            I use color equations a bunch, but they do not use variables.

            Comment


              #7
              RE: Looks like a bug...

              My work around... on the Onchange event for the checkbox.
              ''XBasic
              if var->FLHCALC = .T.
              :Schedule:Checkbox1.fill.backcolor = "Black"
              :Schedule:Checkbox1.fill.forecolor = "Yellow"
              else
              :Schedule:Checkbox1.fill.backcolor = "Black"
              :Schedule:Checkbox1.fill.forecolor = "tanl"
              end if

              Comment


                #8
                RE: A5 confusing a variable ref with a table handl

                the checkboxes color equation is looking for the fhlcalc
                variable among global variables or session variables. you
                have probably defined it on your form as a layout variable.

                Comment


                  #9
                  RE: A5 confusing a variable ref with a table handl

                  Peter-
                  It shows this error for ANY variable. Global, session, you name it. Did you test it?

                  Comment


                    #10
                    RE: A5 confusing a variable ref with a table handl

                    Stephen,

                    Search the board for "color equation" (in quotes). There have been a number of messages and long discussions about this. Your workaround may be the only answer, since color equations don't seem to work correctly on checkboxes.

                    Jerry

                    Comment


                      #11
                      RE: A5 confusing a variable ref with a table handl

                      Try this just for the fun of it
                      if(FLHCALC=.t., crunch_crunch,0)

                      Nick

                      Comment

                      Working...
                      X