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

change or enter mode?

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

  • change or enter mode?

    I have an OnPush event on a form which should trigger calculations based on values entered on the form. I then want to populate fields on the form with the result of these calculations. Unfortunately, the calculations are somewhat complicated by the fact that each summary field is calculated a different way and there are rules which I have coded which account for missing values, etc.

    My question is this: when I try to update the form fields directly using the statement

    t.dailycat = var_dailycat

    where dailycat is the name of the form's control, t is the form pointer, opened with table.current(), and var_dailycat is a layout variable which contains the result of my calculations.

    However, when I run the form, I get an error message that the table is not open in change or enter mode. So, I added a table.enter_begin statement before the above statement and then table.enter_end, but still get errors.

    What mode does the table.current() open the table in? I can read form fields using the t.daily1 method to read the field daily1 with no problem. Why can't I also write using the same method?

    Thank you,

    Dave
    David A. Volgas, MD

  • #2
    Re: change or enter mode?

    Originally posted by davidv43 View Post
    What mode does the table.current() open the table in?
    It doesn't open anything. It establishes a pointer to the currently open table.

    table.enter_begin statement before the above statement and then table.enter_end,
    The syntax would be

    t.enter_begin()
    and then
    t.enter_end(.t.)

    What you probably want is something like

    Code:
    t = table.current()
    if t.mode_get()= 1 then
    t.dailycat = var_dailycat
    elseif tbl.mode_get()= 2 then
    t.dailycat = var_dailycat
    else
    t.change_begin()
    t.dailycat = var_dailycat
    t.change_end(.t.)
    end if
    Last edited by Stan Mathews; 07-25-2008, 02:19 PM.
    There can be only one.

    Comment


    • #3
      Re: change or enter mode?

      David, the user may have begun a change or begun a new record or simply be viewing the current record.

      If you get a pointer to the primary table supporting the form with

      t = current()

      then you can use t.mode_get() to get the mode of the table when the script is running.

      Unless the table is in change or enter mode you can't assign field values to the record buffer, which is what your

      t.dailycat = var_dailycat

      is doing.

      You can read the field value regardless of the mode, but you can't assign a value to the field in the record buffer without placing the table in change or enter mode.

      Naturally, if your table is already in change or enter mode because of what the user has done your script doesn't need to begin a change or enter, any attempt to do so after the change or enter has already started will throw a different error.

      So, long story short,

      change your script to get the mode

      if the mode is 1 (change) then do something

      if it's 2 (enter) then do something else

      if it's 0 (view) then do something else altogether.

      And.... don't forget to refresh any objects in your form displaying field values that are changed.

      -- tom

      Comment

      Working...
      X