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

Is this a bug?? Does anyone understand why this happens.

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

    Is this a bug?? Does anyone understand why this happens.

    I am currently using A5V10.5 4138_3666
    Dbase files.

    Here is the problem..
    Create a new editable grid.
    Put 5 fields in the grid.
    Save the grid. Takes a few seconds.
    Look at the size of the file of the grid and make note of it.
    Mine is around 200k

    Now open the grid and go to properties, Layout Options, Rows of Data.
    Change the default rows to 200.
    Save the grid. Takes about 1 or more minutes to save it and also pegs the CPU to 100%
    Notice the size of the grid file is now 1 meg or larger.
    Notice how long it takes to open about 20 seconds or more.
    Make one change and then save it, takes about a minute or more.

    Look at your task manager, when loading that 1 meg grid file alpha's memory usage will increase 50 to 70 megs.

    Why is alpha doing this?
    Is this a bug or is there another problem.

    Thanks.

    Calyxte

    #2
    Re: Is this a bug?? Does anyone understand why this happens.

    Bumpa

    Comment


      #3
      Re: Is this a bug?? Does anyone understand why this happens.

      Just tried this on a dbf table with only about 600 records, but first build with default 10 record display was fine... saving and displaying in Live Preview... and the grid size was about 121k. Then changed to a record display of 200 and clicked save and it saved exactly the same amount of time as the first time. Grid size is now about 641k. Running the grid is just as fast as in the 10 records display. I see no lag at all. Sounds like something else is wrong... maybe a bad table or re-install your version of A5.

      Comment


        #4
        Re: Is this a bug?? Does anyone understand why this happens.

        Actually David you mentioned exactly what I saw.
        You said with a 10 record display the grid was saved at 121k in size and then with a settings of 200 records was 641k in size.

        Why would the size of the grid change when the settings for the number of records displayed is set higher or lower?

        I know the size of the grid changes when actually displayed but in the development mode we are not looking at the grid itself (unless in a preview mode)
        so the number of rows displayed is just a setting, so why the change in the saved grid size?

        Also you may have a very fast computer try upping the row size to 300 or add a few more fields to the grid. I believe you will experience the same phenomenon as I had, which is a much larger saved file, longer times to open and save the grid and also the huge increase of ram required for alpha to run when that grid is opened. For me it added between 50 to 70 megabytes of RAM.
        Calyxte
        PS I am aware that when the grid is published the speed of running the grid is basically the same whether displaying 10 rows or 200 rows. For this discussion I am mainly interested in what happens during the development process because it really can slow down a system.

        Comment


          #5
          Re: Is this a bug?? Does anyone understand why this happens.

          The grid takes a snapshot of your data, processing it as if you were running live, storing the data in the grid. I don't recall exactly why, but it does use that snapshot for the Preview tab (not live preview or Working preview). It also means your grid will run at about that speed when you do run it live. Look at other web application, Alpha or non-Alpha, they all limit the number of rows to a relatively small number. Or the offer the user the abilty to choose a larger number, at a performance bite. Why do you want to show 200 rows in your grid?
          Steve Wood
          See my profile on IADN

          Comment


            #6
            Re: Is this a bug?? Does anyone understand why this happens.

            No, still not seeing this behaviour. I added another 6 fields and changed the grid to show 300 and then 400 records. Live Preview takes about 2 seconds and same then going to Firefox from Live Preview. The grid size is now 1.7Mb. The save is about the same as well... a second or two. When I change the records back to showing 10 the grid size reduces to 158k... so that's nice. I'd shut down your PC, restart and try again with a new grid... see if you get the same behaviours.

            Comment


              #7
              Re: Is this a bug?? Does anyone understand why this happens.

              Originally posted by Steve Wood View Post
              The grid takes a snapshot of your data, processing it as if you were running live, storing the data in the grid. I don't recall exactly why, ...
              It uses the snapshot in other places - e.g. when selecting a grid using linked content. It shows the image which can be useful if you have a lot of grids and want to make sure you are selecting the correct one. It makes sense then that the grid size changes depending if you are showing 10 rows or 200 - bigger image, more bytes. Not sure why calyxte is having unusually slow save times - maybe the larger grid (image) takes a long time to save on his machine?
              Peter
              AlphaBase Solutions, LLC

              [email protected]
              https://www.alphabasesolutions.com


              Comment


                #8
                Re: Is this a bug?? Does anyone understand why this happens.

                On thing that was mentioned earlier is that this is a security risk if your grid 'has a snapshot' and then you provide that grid to some other developer or otherwise make it available to someone else; they will see that snapshot of data.
                Steve Wood
                See my profile on IADN

                Comment

                Working...
                X