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

Trace event errors

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

    Trace event errors

    Greetings;

    Have a form (3 tabs) that when the form is viewed, the trace log under errors says "add subform link add xxxx." (xxx is the name of the form). There are no subforms. (There is another table that can be opened, but this message occurs regardless.)
    There are 7 browsers involved and under hook errors there are about 18 messages that say "embeddedbrowse activate: cancel selected."
    I searched the 8579 pg help manual for add subform link and found nothing.
    Any ideas where to look. ?

    #2
    Re: Trace event errors

    Are you having trouble with the form or just exploring the trace window? There are many behind the scenes "errors" that do not affect the operation of your application/database.
    There can be only one.

    Comment


      #3
      Re: Trace event errors

      There are problems with the form (actually a browse on the form). Don't really know if it is related as I have been having the browse problem on every form I use when it comes to deleteing a parent with many children. (Keep getting multiple blank records appearing in the browse (parent), which go away if you scroll around (up/down) enough.) Submitted a bug report on this once, pictures/db and all, but never heard anything.
      I did notice that the subform link message appears in regards to many of the forms that are being used through out the app. I would like to know specifically what it means. The though of a behind the scene error not causing problems. ? Who knows, given enough time and/or complexity. ? Which is why I would like to what exactly this means.

      Comment


        #4
        Re: Trace event errors

        Originally posted by milesjg View Post
        There are problems with the form (actually a browse on the form). Don't really know if it is related as I have been having the browse problem on every form I use when it comes to deleteing a parent with many children. (Keep getting multiple blank records appearing in the browse (parent), which go away if you scroll around (up/down) enough.) Submitted a bug report on this once, pictures/db and all, but never heard anything.
        When you delete a parent with multiple child records you have effectively orphaned the child records insofar as the set is concerned. This could explain why the browse lines (child) are emptied of data. I would think that the best practice here would be to confirm with the user that this is what they want to do, delete the parent, then resynch() the form to the tables/set so that the display is updated.
        There can be only one.

        Comment


          #5
          Re: Trace event errors

          Greetings Stan;

          The problem is with the parent browse. It occurs whether or not there are children attached. I have a button which deletes the record in the browse. I used to try to delete a blank record by checking for the particular blank field (in the browse) and using the delete command in the onsave event. Still turns into a mess. A bug report prompted Cian to structure it so that the delete fired inside the onsave, but it created just as big a mess. Anyway, any ideas about the subform add link in the trace window.?

          Comment


            #6
            Re: Trace event errors

            I too had that subform issue in the trace window. I had other problems too because I started changing field names in tables so they would all match. The trace window was a great help. Each time I opened a form it told me where to look for the renamed field. When I finally got to fixing things in the set links, the subform message went away. Don't know if that helps.

            It would be nice if the trace window was documented somewhere. It looks like a very useful tool if I knew what it was telling me. Some of the stuff is self explanatory, but some of it is pretty cryptic.

            Bill Belanger

            Comment


              #7
              Re: Trace event errors

              Bill;

              I still have no idea whatsoever what gives with the subform message. Must not be to critical. You can make one table with one field, make a form with that one field (or no fields for that matter) and when you open it you get the subform link message. I wish one of those mysterious Alpha beings that haunt this message board on occasions would send a sign of some sort in this regards.

              Comment


                #8
                Re: Trace event errors

                I know what you mean James, but I think you can't look at a table or form in Alpha in a vacuum. You think you're just opening that one form, but the trace window is still looking at other stuff, at least that's what I think. Probably the blind leading the blind here...

                Bill

                Comment


                  #9
                  Re: Trace event errors

                  Spoke too soon James. I just added an "on save" event and got the

                  Add subform link add Incoming

                  in the trace window errors. Incoming is the name of the form.

                  Bill Belanger

                  Comment

                  Working...
                  X