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

Regarding memo fields...

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

    Regarding memo fields...

    I'm rebuilding an application that will have eight(8) different tables that will require multiple memo field records for each record in each table. My question is: would it be better (meaning safer in dealing with memo fields) to have 8 separate child memo tables (one for each parent table) or one(1) memo table with 2 separate fields (corresponding to 2 unique fields in each parent table) linking a specific memo record to it's parent table and record? This sounds a bit confusing even to me.
    Here's the idea:

    Parent Table 1 could have record 1 with a unique field entry "F000001" and it's child table could have 25 records linked to "F000001"
    Parent Table 2 could have record 1 with a unique field entry "F000001" and it's child table could have 50 records linked to "F000001"
    And so on for each of the 8 tables. This is the 8 child tables for 8 parent tables scenario. One child table for each parent table.
    Or:
    Parent table 1 could have record 1 with a unique field entry "F000001" and a table identifying field entry "01" with 25 child records linked to "01"-"F000001".
    Parent table 2 could have record 1 with a unique field entry "F000001" and a table identifying field entry "02" with 50 child records linked to "02"-"F000001"
    And so on for each of the 8 tables. This would be the 1 child table for ALL PARENT tables scenario.

    Right now the application has only one parent table with a linked child table for memos and there are almost 300,000 memo records.

    I realize the second method is more efficient and if I were dealing with any other field type except memo it would be the obvious choice, but with 8 parent tables there are going to be a lot more memo records and I'm just not sure whether or not spreading them out over different tables will be safer than lumping all of them in one table.

    Thanks for your input.
    Jim Smith

    Windows 7 OS and v11 possibly switching to v12
    Tags: None
    #2
    Re: Regarding memo fields...

    Regarding memo fields:
    First: if there are 1 or more memo fields in a table, they all go to one fpt file on disk corresponding to that table name. That could confuse me anyhow.
    Best to have a separate table for each memo field with corresponding id field or no more than 2 memo fields. example: main table has id field and each memo table has id field that connects the two.

    connecting> id has entry "F0001", then corresponding memo table id would also have "F0001" as a record.

    I also prefer that "rtfmemo" be used over "memo". I have had less problems with that although, that may be a fluke.
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment

      #3
      Re: Regarding memo fields...

      Dave:
      Thanks for your reply
      I agree with you and do my best not to put any memo fields in a table except when it's simply a matter of the number of characters exceeding the limit in a character field, and then I stick to only one per table. The question is not multiple memo fields but rather one memo field in a single table that has 4 fields: the memo field, a date field and 2 linking fields... that is the child table for 8 parent tables. Or having a separate child memo table (with 3 fields: memo, date and link) for each of the 8 parent tables.
      The first scenario is 8 parent tables and 1 child table. The second scenario is 8 parent tables and 8 child tables.
      JS

      Comment

        #4
        Re: Regarding memo fields...

        I really don't think it is a great idea to have one memo table serving 8 other tables.
        Memo/fpt files fields can grow rapidly in size and can reach 2gig real quick.
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment

          #5
          Re: Regarding memo fields...

          I am curious James on the use of multiple parent tables with the same ID field for linking to the memo fields. Are these parent tables all different somehow or duplicates of each other? Perhaps you will explain the data these parents contain?
          Robin

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

          Comment

            #6
            Re: Regarding memo fields...

            Parent Table 1 could have record 1 with a unique field entry "F000001" and it's child table could have 25 records linked to "F000001"
            Parent Table 2 could have record 1 with a unique field entry "F000001" and it's child table could have 50 records linked to "F000001"
            Color me dizzy! I'm unable to make sense of this. I, and as it appears Robin is, confused how Table 1 and Table 2 can both have a record "F000001" and have it be unique?
            Mike W
            __________________________
            "I rebel in at least small things to express to the world that I have not completely surrendered"

            Comment

              #7
              Re: Regarding memo fields...

              I do understand that his desire is to split up his tables to reduce the size of the linked memo fields. So how to control 8 similar tables with, I assume either have the same data in the parent tables or subsets of the parent data, is his question.

              If he has one parent table with 8 child tables, then a set could show all the memos for each parent. But then I would be concerned how to go about adding any new memos...
              Robin

              Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

              Comment

                #8
                Re: Regarding memo fields...

                On a form on the set. He could have all the memos show if he wanted and they would show all the same record because it is on a set. When he goes to the memo field, the connecting field will fill in. I am working on some of that now.

                I am old fashioned, so I build a form with the id field in plain sight so I can see it fill in. Once form is done, I hide those fields.
                Dave Mason
                [email protected]
                Skype is dave.mason46

                Comment

                  #9
                  Re: Regarding memo fields...

                  I like Dave's idea. However, that being said, I hate (and distrust) memo fields. I only use them when absolutely necessary. If you are not entering large amounts of prose, it may work a lot better if you use character fields. Less likely to give you problems, but you have to make the call. I just don't want to see you heartbroken when the file becomes corrupted and you can't get into it at all. Good luck and be safe out there!

                  Comment

                  Previous template Next
                  Working...
                  X