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

requests for help on the boards and bug fixes

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

    #46
    RE: requests for help on the boards and bug fixes

    Ian,

    ""Just to say I opened the program and a form doesn't sound helpful does it?""

    No but then you only got a general answer which in your case worked out OK. Yes, there are situations like that but they are in the minority.

    Glad it worked for you.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #47
      RE: requests for help on the boards and bug fixes

      Cheryl,

      Just out of curiosity, did you ever coordinate with Alpha Software on the general tips for getting quick responses.
      eg: detailed description, version info & code attachments

      regards,
      Melvin

      Comment


        #48
        RE: requests for help on the boards and bug fixes

        Melvin

        I have found the following to be the best procedure for reporting errors, particularly very odd errors. Alpha has helped the process by including some text on a bug report if you select "Send a bug report" from the help menu. It fills in the A5 build info and asks for the operating system, etc

        1. If you can produce a script or example using AlphaSports, that is the easiest for Alpha or anyone lese to duplicate.

        2. When you have what appears to be a problem, validate that is occurs in some predictable manner and you can repeat the error.

        3. Duplicate the problem on another computer if possible

        4. Doublecheck your code for syntax errors. It is very easy to find what appears to be a "critter" only to later find a syntax error.

        5. If there are any supporting files needed to duplicate the error, be sure to attach them.

        6. When reporting a problem, give a very detailed step by step process to duplicate the problem. I even include lines like "Open A5V6" as sometimes the sequence of actions may be important. For example, a typical bug report I send may look like this;

        --------
        Alpha Five version: 6
        Build: 1536
        Addins: 2010

        Operating System: Win XP Home
        Bug Description: Error when trying to edit existing component in component builder

        1. Open Web_applications_demo database
        2. Open web projects control panel
        3. Select any grid component
        4. Select edit
        5. Click on "fields"

        There are two errors generated. Screenshots attached.
        ---------------

        That was an actual bug report sent for an earlier build of V6. I may also show the results from the interactive window if that applies. A recent example;

        ------------------------
        From the interactive window

        ?now()
        = 10/13/2004 09:57:33 03 pm

        ?now(.T.)
        = 10/13/2004 01:57:34 98 am

        For the second evaluation, the actual GMT date and time should be 10/14/2004 01:57:34 98 am
        ---------------------------------

        One of the keys to good report is to keep the text to a minimum and give a series of very detailed step by step instructions. The instructions should duplicate the error every time. A screenshot of an error message, while helpful, is not very useful if the steps taken to generate the error are not explained. If the problem only occurs in one database or table, try to find a way to recreate the problem in another database or table. If it is a program problem, it should show up in more than one situtation.

        Don't always assume the problem is a program problem. Before sending a report, try to isolate the issue as much as possible. Do routine maintenance like compacting.

        Sending a report that says something like "the darn thing doesn't work" isn't going to help anyone. I have spent most of my working life in service industries and unfortunately, reports like that are all too common. If the person trying to find the problem can't repeat it in a predictable manner, they probably won't be able to fix it.

        Jerry

        Comment


          #49
          RE: requests for help on the boards and bug fixes

          Something else to watch for....

          Some of the things I've found are dependent on whether the form is maximized or "windowed". Almost everything I do is with maximized windows but some people (including Selwyn) prefer windowed forms so it may be worth checking.

          Cal Locklin
          www.aimsdc.net

          Comment


            #50
            As an often "clueless in Seattle" poster, I would like to put an oar in the waters of discontent.

            I completely understand where Cheryl is coming from, and I don't take any of it as being a message board Nazi, but I also see Ray's point. Floating between rank newbie & novice, in my a5 skill sets, I am frequently frustrated by links without an explanation and questions about whether or not I did a search or checked the help files, but the killer is getting a 6 word reply to my novella.

            It sucks when you take the time to TRY to explain the issue accurately & concisely and it's clear, in the response, that the reader used the Evelyn Wood approach to reading it. It goes both ways.
            I'd rather get no response than a lecture, and for awhile there I'd start off each post with a disclaimer "I checked help, did a search, and..." just so I wouldn't have to play 20 questions defending myself before getting to my question.

            Other things to consider, on both sides. We're not all on the same page with regards to the vernacular we use. I understand it's frustrating trying to help people who don't appear to be willing to work for it, but some of us are in France and simply don't speak the language.

            Another is; there are many instances where people don't get a response and stop checking. Happened to me a few times and, when I caught it, I apologized but the point being, my non-response wasn't the result of being an ingrate. I very much appreciate this board and most of the people on it and I'd like to put out an all encompassing THANK YOU to all who have helped, or tried to help me. I'd hate to think what my app would look like if this resource wasn't available.

            Comment


              #51
              Since Bill bumped this thread, I found 2 cents to throw in.

              I purchased v5 when it first came out and it was sooo different from v4.5 that it went on the shelf and I never did get into it. Then v6 and v7. There are so many new features and methods etc. to learn. Even the help documentation can be overwhelming since a lot of it is now for web apps. If Microsoft were not planning on dumping Win98, I probably would have stayed with v4.5. But now that I have gotten my feet wet in v6, 4.5 is in the dust.

              So I started reading the message boards again. This is where I find what I am most likely to want to try. 6 different ways to refresh a browse is not necessary to know IMO, as long as one of 'em works for me! So I will probably be slow to change to new methods unless someone points out a valid use for me. It is however frustrating when something that did work "fine" now will not. This has forced me to rethink my scripts and in the process, find better ways of doing what I was content with before.

              Like learning Xdialog. Talk about Greek! I read the book and still did not get how to do it. So I did the Action Script thing and then started taking the scripts apart (a suggestion from here). This takes time but it works. I actually learned something - though if a ui method works just as well I am inclined to use it instead.

              I would like to see more entries in the Tip section. Someplace we can go for examples. The board is full of zips but finding them is the challenge. This board is getting a lot of activity even though not everyone who views the threads responds. I made one little post and saw 90 hits by the next day. It makes me want to be more helpful when I do post a question or a suggestion, knowing what great company I am among!
              Robin

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

              Comment


                #52
                Originally posted by MoGrace
                I would like to see more entries in the Tip section. Someplace we can go for examples. The board is full of zips but finding them is the challenge.
                Check out the code archive section. In most cases, the code there is very well documented, although you should know some XBasic and getting around in the code editor. There are also sometimes different techniques shown to perform the same process, and that can often be useful info to learn.
                Regards,

                Ira J. Perlow
                Computer Systems Design


                CSDA A5 Products
                New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                CSDA Barcode Functions

                CSDA Code Utility
                CSDA Screen Capture


                Comment


                  #53
                  I have been in and out of the forums for many years. One of the things I have always loved about the Alpha Software community is the willingness to help others. Often, this is someone with a broad working knowledge of Alpha 4 or 5 or both, but on occasion, a relatively new member can post an answer that some of the experienced don't have an answer to. This is great and helps all of us in the long run.

                  However, with all the emphasis on detail and processes to insure you have something to ask or report, I have an observation that might upset some of you detail oriented folks. I am starting to see posts that have an xbasic or script question, the question gets answered, but in many cases, where to put the script is often left out. Should it be on the form init, field event, etc? That knowledge is just as important as the correct answer to the question. And yes, Cheryl, one of the posts I am referring to is the one you had on activation of a field on a subform. I am having the same problem, found the correct syntax for it in reading your post and all its replies, but nowhere do you or those replying say where to put the correct script!!!!

                  Please remember, you may see questions repeated over and over because not All the answer is posted.

                  Thanks
                  Oran
                  My two cents worth :)

                  Oran

                  Comment

                  Working...
                  X