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

Resources going fast, what are some reasons?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Resources going fast, what are some reasons?

    Just introduced an application written about one year ago and the resources go so fast. Most of this application is directly from alphasports.

    1 conditional object
    5 radio buttons that use values to update other fields with
    the onchange event.
    1 Browse for the actual child records.

    Seems to me that if I use the radio buttons (mostly playing with the values to see the fields update) alpha uses all the resources.

    If I enter child records into a browse the resources start to dwindle (rapidly around 15 records)

    How do I slow this down????????

  • #2
    RE: Resources going fast, what are some reasons?


    Without knowing the particulars of the code and what actions are occurring, it is not possible to determine why this might be happening. The newer builds of A5 have reduced resource useage greatly. Some things that could cause recources to dwindle would be dialog forms left open, records left in enter or change mode, tables opened in code but not closed, complex sets with referential integrity that leaves tables open, complex queries, etc. Perhaps if you post an example, someone can give a better diagnosis.



    • #3
      RE: Resources going fast, what are some reasons?

      Funny thing,,,,,,,,,,, I seem to run into these kinda 'resource' problems while using such things as radio buttons, tab forms (I don't use them now) conditional objects and forms with many records (child). That being said, I have never run into this problem leaving tables opened, complex scripts or detailed queries (I seldlom need complex queries).

      I do have a complex set (alphasports invoice set). I will mess around with this. But somehow I think I will have to mess around and see what makes my system happy.


      • #4
        RE: Resources going fast, what are some reasons?


        I had a similar problem until I was convinced to run everything from a
        menu based on a dummy table, and made sure any table, form or report
        was closed when I finished with it. It taught me to keep an eye on the
        available resources. I am now running an app with about 10,000 records
        in it and when it is open my resources drop to 86%, as soon as I close
        it they go back up to 95%.



        • #5
          RE: Resources going fast, what are some reasons?


          The entire problem had to do with the referential integrety. When I omitted this option all was well. Even ran it on a small computer with no memory to speak of and it worked well. Why is this????????/

          I resorted to using xbasic to update all records with child. Lots of work.


          • #6
            RE: Resources going fast, what are some reasons?


            The big problem with referential integrity is, that for it to work, it has to lock all of the child tables whenever the parent is in edit mode. I also understand that when you make a change in the parent, it then must check each child record to determine if the change cascades. All of this takes resources. Many developers, myself included, avoid using intergrity and just code any changes that affect the child. If a set is well designed, the linking field shouldn't change anyway. The only positive use of integrity would be to simplify deletes, but coding to delete child records is very straightforward anyway.