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
Devcon 2020 Goes Virtual! LEARN MORE >

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

JMR would like your opinion !!!

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    JMR would like your opinion !!!

    I would like to get your opinion.

    I am converting an old (1994) A4V6 app to A5V5. I am considering creating a set which would consist of the Inventory.dbf (primary) with linking Purchase Order Items, Receiving Items, Sales Items, Adjustments Items, Transfer Items and Return Items. The reason for doing so is to be able to create calculated fields on a form being the sums of the quantities from each of these dbf's, and further to reflect these values into a calculated On_Hand field on the form. This would provide a "real-time" Inventory On-Hand value, (at least in a calculated form).

    The question (or opinion) that I seek is this...over time, all of these dbf's could become quite large, exceeding 100,000 records easily. I can imagine that when opening this set (form) that one may want to leave for the coffee shop, sit back and relax awhile, as it could take some time before anything displays to screen, (at least initial tests have shown this).

    What's your opinion (experience) with working with large dbf's in a set? Would it be better to use posting rules to the Inventory->On_Hand field?

    Your input is appreciated !
    Tags: None
    #2
    RE: JMR would like your opinion !!!

    Jon,

    I have no experience working with large databases but I can offer this. You do not need a large set so it can be set up with 2-3 smaller sets so that all the table aren't open at the same time. Other comments I've seen in regards to large tables indicate that there should be no lunch breaks.

    No doubt you will get some comments from large users to clarify the issue.

    kenn
    TYVM :) kenn

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

    Comment

      #3
      RE: JMR would like your opinion !!!

      Jon,

      I was told by some very wise people who use Alpha to follow a very simple rule with regard to Sets. For data entry use as few tables in a set as possible. For data retreival use as many tables as needed in the set. Yes it does mean building extra sets with the same tables but that way you get the extra flexability of how you use the data. Also remember that a table dose not have to be in a set if it is just used as a Lookup. Hope this helps.

      Keith Hubert
      London.
      Regards
      Keith Hubert
      Alpha Guild Member
      London.
      KHDB Management Systems
      Skype = keith.hubert


      For your day-to-day Needs, you Need an Alpha Database!

      Comment

        #4
        RE: JMR would like your opinion !!!

        Jon,

        the potential size of your tables is probably not going to be particularly troublesome to you. Wise use of indexes will keep things moving at a quick pace. However, the use of a complex, multi-table set, for your data entry form might not be a good choice, especially if this app is going to be run over a local area network. Track down and read, and then re-read, an article by Dr. Wayne, at www.learn alpha.com called 'Simplify Your Applications'.

        -- tom

        Comment

          #5
          RE: JMR would like your opinion !!!

          It appears to me that many of the tables that you would be opening to retrieve the required data is not necessary if you use a separate table as a summing table. In other words, add the sums from the old tables (past months or years) into calculated fields in a table that stores the required values from past (or history tables), then all you need to do is link to the summing table. I do a similar thing by removing last years data into a history table thereby reducing the current table to a minimum, the history tables can always be addressed when necessary.

          Hope it spurs new thoughts,
          efs

          Comment

            #6
            RE: JMR would like your opinion !!!

            Thanks to all for your comments...they are well taken!

            Comment

              #7
              RE: JMR would like your opinion !!!

              The reason for doing so is to be able to create calculated fields on a form being the sums of the quantities from each of these dbf's

              If you don't need them for any other purpose, try using the DBSUM() and DBCOUNT() functions. And, less common but also useful are the functions: DBMIN(), DBMAX(), and DBAVG(). I think you will find them to be just as fast and it may significantly reduce the complexity of your set(s).

              Comment

                #8
                RE: JMR would like your opinion !!!

                I have done and use both of these methods in A4v6. For some cases the summary of child records is useful but it does get VERY slow with large number of child records. If speed is of any concern use the posting. Going forward in a5 I am going to change this to make it faster where possible and redesign this in other places to speed it up.

                Russ

                Comment

                  #9
                  RE: JMR would like your opinion !!!

                  Hello Jon,

                  If you have a table like this:

                  Inventory.dbf
                  Fields:
                  Orderno
                  Ordertype
                  Orderdate
                  (Item)
                  then you have to get data from the linked other tables.

                  If you have also the field: Quantity
                  And you have a table e.g. ITEM
                  Fields:
                  Item
                  Description

                  Then you make a set with Item as parent and Inventory as a child.
                  Now you can index/filter the data by item and have (summary) totals on quantity.
                  For that info you don�t need all the link-tables.

                  If you have to many records in your table you can copy them into a backupfile and make a summarization by item. e.g. year, month. Append the summarization records into your inventory table and delete the records you copied to that backupfile. You�ll enjoy it (again)!

                  Ton Spies
                  Most things are simple but unfortunately only after the first time

                  Comment

                  Previous template Next
                  Working...
                  X