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

subelement not found

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

    subelement not found

    below is part of the script I ran. this worked before but now it is giving me an error saying "tbl_changed.effdate subelement not found"

    tbl_changed = table.open("changed_main")
    tbl_changed.enter_begin()
    tbl_changed.Effdate = tbl_new.Effdate tbl_changed.region = tbl_new.region
    tbl_changed.stock1 = tbl_new.stock1 tbl_changed.stock2 = tbl_new.stock2
    tbl_changed.enter_end(.T.)
    tbl_changed.close()

    error occurs at every field. what does "subelement not found" mean?

    #2
    RE: subelement not found

    Trixie,

    looks as though your line breaks have gone on walk about.

    tbl_changed.Effdate = tbl_new.Effdate tbl_changed.region = tbl_new.region
    tbl_changed.stock1 = tbl_new.stock1 tbl_changed.stock2 = tbl_new.stock2


    These should be 4 lines, not 2

    -- tom

    Comment


      #3
      RE: subelement not found

      Trixie

      I hope your code is actually

      tbl_changed = table.open("changed_main")
      tbl_changed.enter_begin()
      tbl_changed.Effdate = tbl_new.Effdate
      tbl_changed.region = tbl_new.region
      tbl_changed.stock1 = tbl_new.stock1
      tbl_changed.stock2 = tbl_new.stock2
      tbl_changed.enter_end(.T.)
      tbl_changed.close()

      rather than all on one line as you posted it. If two fields are listed on one line, that would probably give the error. About the only other reasons you would get the error are if there are no fields in the "changed_main" table or the table with the pointer "tbl_new" is not open in the script. The error indicates that the program can't find an element (i.e. field) for the tbl_changed pointer.

      Jerry

      Comment


        #4
        RE: subelement not found

        Jerry,

        You are right what my code should be. I don't know how it got posted that way.

        Jerry Brightbill wrote:
        -------------------------------
        About the only other reasons you would get the error are if there are no fields in the "changed_main" table or the table with the pointer "tbl_new" is not open in the script. The error indicates that the program can't find an element (i.e. field) for the tbl_changed pointer.

        I will try to look into this. Thanks a lot.

        Comment


          #5
          RE: subelement not found

          Hi Jerry,
          thanks for the reply but have check what you've suggested and it seems fine. don't know what is wrong...the code worked before but now is giving me the "subelement not found" error.
          I have attached the code, could you (or anyone) please take a look and tell what I am not seeing.
          Many Thanks. Trixie.

          Comment


            #6
            RE: subelement not found

            I think you are missing the "then" part on all of your "If"s.
            If then
            statement
            staments
            else
            statements
            end if

            Hope this is the case!!!
            The Mexican

            Comment


              #7
              RE: subelement not found

              Trixie

              The lack of the "then" at the end of the line for the if statement is optional and should cause no problem. Usually the "subelement not found" would indicate that some field or table reference can not be found rather than a specific problem with the code itself. Posting the tables with some dummy data would also be helpful.

              I do see that your code opens the table, but doesn't close them. I would assume that the posted code is not complete. Some of the logic is unclear to me. You zap one table "changed_main" to clear it, but then enter the changed records into "nat_changed_ptpn". Is that correct? Also, what is the purpose of the "!" in the expression? If this part of a field name?

              One problem that shouldn't cause an error, but is very inefficient, is how you are fetching thru the tables. It appears you are fetching thru the complete "new_main" table for each record in the "main" table. Even if the number of records is small, there are better ways to fetch the related records. You already have both tables set with the same index, so you could use a find() to get tjust the records that match. Attached is text file with an example showing how to fetch thru the tables quicker.

              If you post the tables and the complete script, it would be possible to use debug() to try to isolate the problem.

              Jerry

              Comment


                #8
                RE: subelement not found

                Trixie,

                I was looking at your code and saw something funny. Did you actually mean
                tbl_old.street!

                or was it

                tbl_old.street1

                That darned shift key can kill you, especially in a large script.

                Comment


                  #9
                  RE: subelement not found

                  != as in ">
                  There can be only one.

                  Comment

                  Working...
                  X