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

Memo field - Changing set relation

  • Filter
  • Time
  • Show
Clear All
new posts

  • Memo field - Changing set relation

    I have a material invoiceing program that consists of 4 databases as follows:
    1. Customer File
    2. Job File
    3. Invoice Header File
    4. Invoice line items file

    These are all related one after the other in a one to many relation. Each customer can have multiple jobs, each job can have multiple invoices, and of course each invoice can have multiple items. Real simple so far.

    These are on a tabbed form with embedded browses. The first tab has three browses to pick the customer, job, and invoice that you wish to work on. Then on the second tab is the invoice line items browse where you can add line items to the chosen invoice. Works great. I put a button on the invoice detail screen to print the current invoice.

    Then I thought it would be helpfull to add a memo field to hold a description of the work performed so it would print on the invoice also. I added it to the invoice header database as there would only be the one description per invoice and added a field on the form where it can be edited. Now the trouble starts.

    Anytime there are multiple jobs for a given customer, when notes are added to the memo field, that invoice is reassigned (the link field of the set definition is reassigned) to the first job for that customer which of course is incorrect.

    Why does editing the memo field change the linking field information?? I can edit any other field on the invoice header and it makes no difference. I have noticed that if I edit the memo field with the memo field editor that works OK but not if I edit in the display field. Any ideas??

    I've tried compacting the database, packing the files, reindexing, etc. but nothing seems to help. I could send the stuff if someone thinks they could figure it out??

  • #2
    RE: Memo field - Changing set relation

    There have been multiple postings regarding memo fields and the problems that some have encountered when using them. Try changing your memo field to a character field of specific length, say 40 characters, and see if you experience the same problem.

    If the problem goes away, hope that Alpha 5 v5 is more reliable in regards to memo fields. Mayhap they will go the way of ask user variables, available but not supported.
    There can be only one.


    • #3
      RE: Memo field - Changing set relation


      Just dropping a field from the invoice header table on to the tab does not provide the necessary synchronization to the correct record in a one-to-many relationship with the Customer table. While the child field is "raw" on the tab I would expect that the memo would be added to the first child record. In general, only fields from the parent table should be added directly to a tabbed subform; fields from child tables should be either in browses or sub-forms.

      You could:
      1. Add the memo field to the browse
      2. Add a subform to the tab which contains only the memo field
      3. Drop the memo field from the invoice header table and create a new table with 2 fields; a link field based on the invoice number and the memo field, then add this table to the set in a one-to-one link to the invoice header table then add a subform based on the new child table to the tabbed sub-form.

      I'd say that 3 is the best solution. Some people use memo fields and never have a problem. This way, though, if a problem should arise, it won't affect the header or details tables. When a memo field goes bad in one of your main transaction tables ... well you don't want to know.



      • #4
        RE: Memo field - Changing set relation

        You Wrote:
        Try changing your memo field to a character field of specific length, say 40 characters, and see if you experience the same problem.

        No, that works fine, although then I don't have the dynamic sizing of a memo field. These descriptions vary from a few words to a half page or more and if I add multiple fixed length comment fields then formatting would also be a problem during print.

        I hope they are doing something with the memo fields to make them useable. I've done a search on them in the forum and they seem to be more trouble than there worth. Other database programs use them and there just isn't any way to do this cleanly without them.

        I am still trying to find a work around. I'm never sure if my problem is me or if there's a quirk in the Alpha Code. A person can burn up lots of tme on these things.

        Sign me off as FRUSTRATED!!


        • #5
          RE: Memo field - Changing set relation

          Thanks Finian,

          I tried your third recomendation and it works great. I don't know that I understand why it didn't work the other way but, hey, if it works I'll move on.

          I just need to revamp my report now which should be no problem and then we're off and running!

          Thanks Again