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

Proper Table Referencesin Set

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

    #16
    RE: Proper Table Referencesin Set

    Greg,

    I use f2.activate(), then f2.show(), then f2.close() because that's the way more experienced folks have done it. If you don't have any problems leaving it out I'd say that's ok. You might want to test whether the dialog form is actually closing if decide to do this.

    Concerning resynch(), I did not do any actual editing in my work last night. You may need to include it to get the edits to display in the original form. Try it both ways, and again, verify that the dialog is actually closing.

    -- tom

    Comment


      #17
      RE: Proper Table Referencesin Set

      Tom,

      I am always behind.

      Jerry

      Comment


        #18
        RE: Proper Table Referencesin Set

        Thanks Tom,I will try it with f2.activate(). With regard to the example, I recall somewhere that I had some trouble when the parentform was not hidden. After hiding the parentform the problem disappeared.

        Comment


          #19
          RE: Proper Table Referencesin Set


          Greg, you're welcome.

          I make it a personal rule to ALWAYS check to verify that the called dialog form has closed when modifying a script which loads or opens one. You can do this in xbasic, or you can just check the Xbasic Explorer after opening the dialog several times in a row.

          -- tom

          Comment


            #20
            RE: Proper Table Referencesin Set

            OK I give up, how do you check for open dialogs with xbasic?

            Comment


              #21
              RE: Proper Table Referencesin Set

              Greg,

              Just like you would test to see if any other object exists, I suppose. Have you tried Obj() or Is_Object(), as discussed at the end of chapter 6 of the Xbasic Ref. Manual?

              I routinely check to see if a form is already loaded, before loading it again. If it's loaded I don't bother, I just work with the instance that already exists. If it's not yet in existence then I load it. I've assumed the code could be easily modified to check whether a dialog form remains open.

              Assume your dialog form is named 'Customer':

              p = obj(":Customer")
              if .not. is_object(p) then 'form is not loaded
              ui_msg_box("Ok","Form was closed")
              else
              ui_msg_box("Oops","Form is still open")
              end if

              -- tom

              Comment

              Working...
              X