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



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

Me too I have a slowness issue

  • Filter
  • Time
  • Show
Clear All
new posts

    Me too I have a slowness issue

    My slowness is due to the nbr of records in my emb browse and getting worse as I add more child records and don't know how to correct it. Please see attached pdf.

    Re: Me too I have a slowness issue

    Gaby, your attachment is a good example for us all. Thanks for presenting it so clearly.

    1) Active link tables, or native DBF tables?

    2) Assuming native tables, check the performance of the "default form" for your set. It will use embedded browses that do not have the calculated columns you mention, and should run faster. Comparing the "default form" with your custom form will give you an indication of how much drag is being caused by the calc fields (columns) in your browses.


      Re: Me too I have a slowness issue

      Thanks your reply. Yes all my tables are native tables, no active link at all.
      Yep, the performance in the default form is blazing fast. I suspected my calc fields were partly responsible for the slowness. I moved the calc fields out of the emb browse and placed them on the form. It's a bit better, but worry when there will be many more records in the emb browse.


        Re: Me too I have a slowness issue

        Lookup() and Tablecount() are among the slowest functions. They each require Alpha to open a new instance of a table, do some processing, and return the computed value, and then close the table. This sequence gets repeated each time these functions are called. If you use them in a calc field "column" in an embedded browse the entire sequence is repeated, separately, for each linked child table record, whether visible in the browse object or not. Performance will be affected by the number of linked child table records, obviously, as well as the speed of the hardware components, especially the network cards and cabling.

        In "slow" environments the goal should always be to minimize traffic on the network.

        Design questions that can affect performance:

        a) do you really really need to see the lookup and tablecount data for each registration record, all the time? if not, don't put the calc field in a column of a browse object, but compute it on a button push, only when the data is needed.

        b) can you tolerate a bit of data redundance in your system? if so, store the firstname in the registration record during data entry, either by calc field or by user entry.

        c) the aggregate (summary) computations can be replaced using a post field rule defined in the transaction table. Each time an event occurs (registration, attenance, invoice) a running total field in the customer record gets incremented, for example.

        Food for thought.

        -- tom
        Last edited by Tom Cone Jr; 11-09-2009, 06:50 AM.


          Re: Me too I have a slowness issue

          Thanks Tom for your explanations. I have been using these functions without really knowing how they work behind the scenes. Now I see. I can now redesign the set and calc fields in light in your input. Thanks again.


            Re: Me too I have a slowness issue

            Just another angle to think about.....

            If you can create / modify your indices so you can use dbcount(), dbsum(), etc - I think you will see big performance improvment since those functions use an existing index to make their calcs instead of opening another instance of the table as Tom had mentioned.

            I have a form in one app that makes extensive use of the various db functions over a network and it is actually pretty snappy.....probably 10 different db sumns or calcs on that one form (as reference for you so you might use that number as a baseline). I am not sure how many you need.




              Re: Me too I have a slowness issue

              Hi Jeff:
              Totally forgot about the DB functions. Thanks for the tip.