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

Safe embedded browse entry at last in A5V5?

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

    Safe embedded browse entry at last in A5V5?

    Has the holy grail of direct embedded browse record entry been found in A5V5? My record entry procedure requires that the user enter new records through a form. The new record is created in xbasic first before the form is opened. This requires a lot of mouse clicking. The users have been harping about how slow it is to enter records. They prefered to enter directly through a browse but I like the relative safety of the recommended method that I have in place. Are their new features in the new version that will give my users what they want?

    #2
    RE: Safe embedded browse entry at last in A5V5?

    Greg,

    --The new record is created in xbasic first before the form is opened. This requires a lot of mouse clicking.--

    Ya lost me. If you're using xbasix to set the form so that it opens in new record mode, I don't understand why there should be any mouse clicking.

    --The users have been harping about how slow it is to enter records.--

    This sounds like you have other problems. Is this on a network? If so, I'd look to network issues. Also, if there are only a few fields to enter, not any more than what fits on the screen, a browse is very beneficial to use for data entry. There is no problem with that. I do it all the time.

    In answer to: Are their new features in the new version that will give my users what they want?....There's a big imporvement in the use of memo fields in a browse. Perhaps yu could identify the specific issue that's causing the problem??

    kenn
    TYVM :) kenn

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

    Comment


      #3
      RE: Safe embedded browse entry at last in A5V5?

      Greg:

      I have dozens of embedded browses in use every day in several applications. They all work without flaw. I even have a couple applications out there written in A5 Version 1 that have been in use for years now, every day, with no problems.

      I have seen hints that others believe there to be problems with entering through embedded browses, and would love to see an example of a problem. Can you post something?

      I know there are a couple bugs in A5, and don't dismiss that something may be wrong, but it is clearly only under certain unusual circumstances. At least by my definition of unusual.

      Granted, there are times where a popup child form works better, but for faster data entry, which is most often in demand, nothing beats the embedded browse.

      OK, while I'm purging, I've never had a problem with memo fields, either. Again, not that I'm saying there isn't a problem, but if there is, it's only under certain situations.

      I think it may be late in the game to start with version 4.5, if these issues are resolved in version 5, but I would love to know what gives, and why.

      Anyway, I'd love to see an example. It would be interesting to isolate why some say they don't work.

      Again, I'm not saying the bugs aren't there. I recently found a major bug in version 4.X (Shadowed databases don't detect if a table is in use, so zapping is unreliable.), but I am still able to use shadowed tables!

      Craig

      Comment


        #4
        RE: Safe embedded browse entry at last in A5V5?

        Greg,

        There should be almost no need to use the mouse on a form, especially if you set the tab prompt order on the form. Have you tried this?

        Your issue with browses is unclear.

        Regards,

        Ira J. Perlow
        Computer Systems Design & Associates
        [email protected]
        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


          #5
          RE: Safe embedded browse entry at last in A5V5?

          Craig,

          Perhaps Greg was referring to the fact that the A5v4 browse object does not give you as much control over the data entry process, as does using a single record form. (for example, events which fire when moving from column to column) I'm hoping the A5v5 browse object has been changed to expose more of the underlying events to the Xbasic programmer.

          -- tom

          Comment


            #6
            RE: Safe embedded browse entry at last in A5V5?

            Thanks Tom, the access to Xbasic is really what I am after.

            Comment


              #7
              RE: Safe embedded browse entry at last in A5V5?

              And on the subject of memos, I have just experienced the unnerving experience of corrupt memos. I am going to try separate linked memo tables this time. This scheme seems much more practical now in light of the fact that the new version will have such a nice backup facility. Now if only I could find a way to test for memo corruption!

              Comment


                #8
                RE: Safe embedded browse entry at last in A5V5?

                Greg, and Tom:

                I stand corrected, then. "Safe embedded browse entry" as a title was more than deceiving, and "the relative safety of the recommended method that I have in place." didn't help, either.

                Then again, I learned to read off the back of a Froot Loops box...

                Greg, I would look into alternative choices. Perhaps the events associated with the field rules are an option. I don't remember any actions in version 5 that are specific to a column in a browse, embedded or not, but I didn't really look, either... The mouse clicks leave me wondering...

                Craig

                Comment


                  #9
                  RE: Safe embedded browse entry at last in A5V5?

                  Ahhh, 'Froot Loops'... remember them well.

                  -- tom

                  Comment


                    #10
                    RE: Safe embedded browse entry at last in A5V5?

                    "Oots-Fray Oops-Lay" I know what it means!

                    --Ira
                    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

                    Working...
                    X