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

Vers. 1.02 Conversion Problem

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

    Vers. 1.02 Conversion Problem

    When I converted my Stamps application from version 1.02 to 4.5, I get the following error when I start up the application:

    Script: Table(REGULAR)OnEditField Line 0
    Table not in change or enter mode

    on the first field on the screen when trying to open up the Stamps form. It is a key field which is a link to the Catalogue table. Anyone have any idea on how to fix this problem or where I would find out more information on this message? The Help tutorial is of no use.

    The Set is defined as follows:

    Regular
    |
    |
    +----- Catcan Linking field CATAL_NO
    |
    |
    +----- Stdesc Linking field IDENT

    The following events are present for the REGULAR set on the CATAL_NO field:

    OnEditField
    -----------
    REGULAR->CAT_NO_A = CATCAN->CAT_NO_A
    REGULAR->CAT_NO = CATCAN->CAT_NO
    REGULAR->SUB_NO = CATCAN->SUB_NO

    OnWroteField
    ------------
    REGULAR->CAT_NO_A = CATCAN->CAT_NO_A
    REGULAR->CAT_NO = CATCAN->CAT_NO
    REGULAR->SUB_NO = CATCAN->SUB_NO

    Thanks,
    Ron

    #2
    RE: Vers. 1.02 Conversion Problem

    You have to explicitly put the tables in change or enter mode, after first obtaining a table pointer. I think you'll need the following for both events


    tbl1 = table.current(1)
    tbl2 = table current(2)
    tbl1.change_begin()
    tbl1.CAT_NO_A = tbl2.CAT_NO_A
    tbl1.CAT_NO = tbl2.CAT_NO
    tbl1.SUB_NO = tbl2.SUB_NO
    tbl1.change_end(.T.)

    There are likely other was to do this, but this should work.
    BTW if you need to refer to the stdesc table, it would be table.current(3).
    There can be only one.

    Comment


      #3
      RE: Vers. 1.02 Conversion Problem

      Thanks Stan. I tried your suggestion and still got the same error. I would have thought that when the form was converted that the correct code would have been generated.

      Comment


        #4
        RE: Vers. 1.02 Conversion Problem

        Stan, sorry about that. For some reason my changes did not get saved. I tried it again and it seems to work okay.

        Thanks for your help.
        Ron

        Comment


          #5
          RE: Vers. 1.02 Conversion Problem

          Glad to help. I went back to review "form methods" which seem to be mor like what your original was and found:
          This next example contrasts the "tbl>.change_begin() method (which works
          with tables �behind the scenes�) with the form methods for changing the record
          that is currently displayed on a form. This script could be on a button on a form.
          Note that, just as when you are editing data in a form, there is no need to
          explicitly put the form into change mode. As soon as you change the value
          property of the Last_name control, the record is automatically placed in change
          mode.
          Last_name.value = �Washington�
          First_name.value = �George�
          parent.commit()

          Which I believe means your original could be modified to:

          REGULAR->CAT_NO_A.value = CATCAN->CAT_NO_A.value
          REGULAR->CAT_NO.value = CATCAN->CAT_NO.value
          REGULAR->SUB_NO.value = CATCAN->SUB_NO.value
          parentfom.commit()

          But if the other works...........
          There can be only one.

          Comment

          Working...
          X