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

Quirky Tool Bar behavior in Runtime

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

    Quirky Tool Bar behavior in Runtime

    I have a form whos On Init Event puts the form in query mode topparent.query_by_form()
    The form has 2 tool bars. One for query things like Run Query topparent.query_run()
    Another for Exiting Query Mode
    topparent.query_exit()

    The other tool bar has basic navigation stuff like
    topparent.Fetch_First()
    topparent.Fetch_Prev()
    topparent.Fetch_Next()
    topparent.Fetch_Last()
    topparent.new_record()
    and
    topparent.query_by_form() to go back to query mode

    My problem is that if the query does not find any matching records (No records were found) the form goes back to View Mode and it loads 2 copies of the View Tool bar, one above the other. The lower one works but the upper one does not. If I then go to Query Mode the upper one stays (still not working) and the Query tool bar shows (which works). This only happens in the Run Time.

    Any ideas?

    Scott
    Scott Peterson, MCSE, MCP+I, CLP
    S/P Systems
    Cincinnati, OH

    #2
    Correction

    I have since found that this only happens when the QBF Helper is turned off. My users turn this off but I do not.
    Scott Peterson, MCSE, MCP+I, CLP
    S/P Systems
    Cincinnati, OH

    Comment


      #3
      Do I get the stump the experts award

      Since I haver not gotten a single reply on this I guess I win the Stump the Experts award. Alpha has not even replied.

      Scott
      Scott Peterson, MCSE, MCP+I, CLP
      S/P Systems
      Cincinnati, OH

      Comment


        #4
        I guess I've become my father. Never thought I'd hear myself saying that!

        I prefer to communicate with folks who use their real names. Personal preference. No offense intended.

        A more likely explanation is that your post seems to involve a complex form, yet you haven't made it easy for us to see the problem. Posting a working model of the database, with instructions for us to follow to see the issue would be a BIG first step in getting help.

        -- tom

        Comment


          #5
          Scott aka scooby ( sorry, My sentiments on this follow those of Tom)

          What by definition is 'QBF Helper' - do you mean 'Querie Genie' ?

          Colin

          Comment


            #6
            If the answer to the above is YES and you are invoking both Genie & QBF by the oninit then you are attempting to ask for two queries at the same time. NO GO. Use either one or the other. If you try this on a form using the standard toolbars you will see two query tb's. If you close the Genie with its close button both qery tb's remain. If you then run the query by using the form one Q tb remains but inactive and won't go away until you change the script. You may be experiencing some thing similar with your custom tool bars ( or are your toolbars not custom built but just rows of individual buttons?)
            The real question is - Why query on init? Why not just let the user poke the QBF button as required and save youself a load of hassle?
            There again, you may have excellent reasons for doing it your way, but still have the hassle. My maxim is "keep it simple" for me as well as the user - but compromises can often be far from simple :)
            Colin
            Last edited by Colin Roberts; 10-06-2005, 07:22 AM.

            Comment

            Working...
            X