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



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

Displaying a .value

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    RE: Displaying a .value

    .. and I'm still getting that "no such field" error. What on earth can that mean? This is such a simple little form that I can't see what could possibly have gone wrong.


    • #17
      RE: Displaying a .value

      No Ken, I'm sure you're right, in fact you are 'cos I've tried it. The only problem with that solution is that the user can go into the form at any time and change the room, the type of room (selects a room name but via type or room), the arrival date and/or the departure date. I would have to attach the code to every field. OK, not impossible, but inevitably when creating the record for the first time, some of the "other" fields won't be entered yet, so I'd have to build in so many conditions that it seemed more elegant to simply check, on the Save button, firstly that all the mandatory fields are completed, and then do the calculation once.

      Surely I'm not asking for the impossible? (I'm a newbie, too, but I have aged quite a lot over the last few months!)

      Thanks, again, Ken, and everyone.


      • #18
        RE: Displaying a .value


        ..."They can change anything any time....."

        Could field rule validation help? Couldn't these make the record unsavable unless all of the information in each field was tested?

        I didn't try the form/variable trick with an 'On arrive' event for the save button, I'll try that and get back to you.



        • #19
          RE: Displaying a .value

          The record IS unsavable unless all essential fields are completed, as I've built this into the Save button (BEFORE the room cost calculation). I don't think field rules can help because, again, validation of room availability is required, which means examining current reservations, season details, etc, etc. there isn't one easy rule. Having said that, I've got all of that (room availabilty checking, calculation of room prices, agent's commission, etc.) to work (and quickly!)

          All I want now is to be able to display a value on a form when a button's pressed. Some people want it all, don't they...?

          Thanks for sharing these moments with me Ken.

          How long have you been a fellow-sufferer?



          • #20
            RE: Displaying a .value

            Of course you are not asking the impossible. It should be simple.

            Here is my sample. It is so much like yours there is nothing to explain. Your old form is there. My new one has been added. Note that I just now increased the width of the code field to hold the contents you are attempting to place in it.

            Bill Hanigsberg


            • #21
              RE: Displaying a .value

              I at a client site and will not be able to get back to this until tonight. But I took a quick look and noticed you did not take my suggestion to use the text properties.
              Try this for now:'Date Created: 15-Jul-2002 01:17:25 PM

              f = parentform.this
              ''numero = parentform:number.value
              numero = f:number.text
              ''nom = parentform:name.value
              nom = f:name.text
              ui_msg_box("msg box",nom + space(1) + numero)
              ''parentform:code.value = upper(substr(nom,1,3))+str(numero)
              f:code.text = upper(nom)+ numero


              • #22
                RE: Displaying a .value

                Steve and Martin,

                Steve is right of course but I Martin's code works (though arguably it shouldn't) using the value property rather than text and without the parentform alias.

                I know because I tried it every which way on the form he supplied. But his button with code attached worked on a new form.

                Bill Hanigsberg


                • #23
                  RE: Displaying a .value

                  Sorry Steve, I did try .text but to no avail at the time. Probably whatever's wrong with .value is also causing problems with .text.

                  I'll continue to try eveyone's kind suggestions and let you all know if I make any progress.

                  Thanks, all, again, and try not to let my little problems ruin your weekend....!



                  • #24
                    RE: Displaying a .value

                    Hello Martin,

                    Your form is real flaky. My guess is it's the name, and specifically the apostrophe. If you copy and paste, and rename the form some nice simple single word name, such as 'testform', the flakyness goes away. If I rename the form, but leave an apostrophe in the name, then it stays flaky. In general, stay away from spaces and special characters when naming your fields and layouts.

                    In general, I much prefer to write directly to the table by getting a pointer such as:

                    t = table.current()

                    I have much less trouble, even with your flaky form, this method works fine. But that is a different story.

                    Also, your syntax is a bit off. I'd write it something like this:

                    vptr = parentform.this
                    numero = vptr:number.value
                    nom = vptr:name.value

                    vptr:Code.field.readonly = .f.
                    vptr:code.value = upper(substr(nom,1,3))+alltrim(str(numero))
                    vptr:code.field.readonly = .t.


                    Your expression was leaving blank spaces from the numero field, so I trimmed them out. You don't need to unset and reset the readonly property, but it seems reasonable to me to do it.

                    Good luck,



                    • #25
                      RE: Displaying a .value


                      You're right about the apostrophe! I re-named it and it worked (after I'd trimmed the number, of course). The original form that I was having the problem with has an underline in it's name and when I remove this it works! (Actually, at the moment the values appear, and then disappear, but I think I can sort that out on my own!)

                      Well done! I have a couple of other forms in the application with underlines in the name, so I'll change these before anything horrible happens to them.

                      Thanks again; it's something I'll certainly bear in mind in the future. And thanks to the many other respondents; we got there in the end!

                      (a much happier) Martin.


                      • #26
                        RE: Displaying a .value


                        Looks like a candidate for a 'Tip'. Why not write it up and send it to Cal?

                        -- tom