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

errors drop users to control panel

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

    #16
    Re: errors drop users to control panel

    Just a thought, I don't have much experience with errors.
    There can be only one.

    Comment


      #17
      Re: errors drop users to control panel

      Originally posted by Stan Mathews View Post
      Just a thought, I don't have much experience with errors.
      Good one Stan!!!! Probably right too, compared to the likes of me and a whole lot of others.

      Raymond Lyons

      Comment


        #18
        Re: errors drop users to control panel

        chetongueek, naturally.

        Another thought.

        Have the autoexec script include


        on_database_exit(":a5.close()")

        May not be any better.

        Note: I copied and pasted from your post but it is :A5.Close(), not :A5_Close().
        Last edited by Stan Mathews; 02-27-2015, 10:49 PM.
        There can be only one.

        Comment


          #19
          Re: errors drop users to control panel

          Yes, I typed :A5_close() in my message above but it was :A5.Close() in the autoexec, so that had nothing to do with the problem.

          I tried on_database_exit(":a5.close()") but at least as part of the error_handler it cured nothing.

          I am not going to worry about this any longer, mainly because I do very little development anymore.

          Comment


            #20
            Re: errors drop users to control panel

            I gotta ask an obvious question... Do you have a hotspot or hot key combo that would expose the CP?
            Robin

            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

            Comment


              #21
              Re: errors drop users to control panel

              Did you hide it like this??

              hidecontrolpanel.png
              Dave Mason
              [email protected]
              Skype is dave.mason46

              Comment


                #22
                Re: errors drop users to control panel

                Hi Dave
                Yes, as well as in the autoexec

                but the salient aspect of this is that you cannot trap this with an error handler
                Cole Custom Programming - Terrell, Texas
                972 524 8714
                [email protected]

                ____________________
                "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                Comment


                  #23
                  Re: errors drop users to control panel

                  I have had the issue a couple times. I can't remember what corrected it, but it seems it was a pathing issue in my case. Old Body, Bad memory.
                  This is all I have in autoexec for the control panel.
                  a5.Maximize() 'maximize the whole thing
                  controlpanel.Maximize() 'max the control panel even though it is hidden, it makes the forms start as maxed.

                  It seems there was another thread in here of similar nature where it was worked out to not have cp hid both ways?
                  Last edited by DaveM; 02-28-2015, 12:59 PM.
                  Dave Mason
                  [email protected]
                  Skype is dave.mason46

                  Comment


                    #24
                    Re: errors drop users to control panel

                    In the runtime I maximize and then hide
                    I use full screen apps
                    Cole Custom Programming - Terrell, Texas
                    972 524 8714
                    [email protected]

                    ____________________
                    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                    Comment


                      #25
                      Re: errors drop users to control panel

                      Martin,
                      I am saying that I do not hide in the autoexec at all. Have you tried that. I remember it being discussed that could cause a similar issue to what you have. I just can't find that post right now.
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment


                        #26
                        Re: errors drop users to control panel

                        Originally posted by martinwcole View Post
                        Hi Dave
                        Yes, as well as in the autoexec

                        but the salient aspect of this is that you cannot trap this with an error handler
                        As I wrote in an above post to this, in some situations I can trap my type of error (probably very different from what Martin has dealt with, thus my experience is an apple to his orange) and :A5.Close() keeps the CP from being dumped into. In other start up situations, no, or at the very least the start up form opens (when set to open in database properties) when I would not want it to, i.e., I would not want the app running given the error state. And yes, I do use a hidden hotspot to access the CP. And no, it does not seem to matter how I hide the CP. Finally, yes, maybe I should not open the start form via database properties (that might prevent the start form from opening--if the error trap worked!).

                        Bottom line: I think Martin is basically correct: There seems to be no foolproof way to trap certain things in an error handler (at least in an autoexec), and when the trap fails either the CP or the opening form may be shown, either of which may be very undesirable.

                        Raymond Lyons

                        Comment

                        Working...
                        X