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

Confirming Posting Rules

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

    Confirming Posting Rules

    I am working on several tables with common links. I was trying various methods of posting to each of the tables and just wanted to confirm if my thinking was correct.

    From what I discovered you can only post from 1 table directly to another table only.

    What I was wondering (because I have yet to make it work) was if you could post something from the first table to the second table and that same field from the second table to a third table instead of post directly from the first to the third?

    Example

    Table 1 - Field 3 is a calculated field (value of Field 1&2)

    Table 2 - Field 3 is posted from table 1 (child table of #1)
    This is now my main reference field (field #1 in table #2) for the rest of the tables to draw from.

    Table 3 - Field #1 is posted from table 2(child table of #2)


    What I found is that nothing posted to table 3 but if I changed the posting from table 1 to table 3 it worked. So am I correct to assume that you can't cascade post a field through tables or can you and I am doing something incorrectly?

    Any advice would be greatly appreciated.

    Thanks Sue

    #2
    RE: Confirming Posting Rules

    Susan, yes, I think you've reached the right conclusion. However, it shouldn't be too hard to develop a custom post script to stick the necessary value in the right record of the 3rd table. Might be a bit tricky to figure out when the script should run, but it seems to me that table one's OnSaveRecord event (in field rules) might be a good place to start. A lot depends on the nature of the app and the field values involved.

    I rarely post to child tables, personally, because there's uncertainty whether a child table record is already there to be updated. Most of my posts go the other way around, from child to parent, since I know there will always be a record there to receive the new value.

    -- tom

    Comment


      #3
      RE: Confirming Posting Rules

      Thanks Tom

      I thought I was going crazy at first with my main database because I didn't realize the problem. It wasn't until I created a simplified test database and recreated all the different scenarios that I discovered my problem. Atleast I know now, for the future.

      The reason I guess I was doing the posting in reverse of the norm is because I have different codes (nrt, par, msl)which I want to create their own individual auto incremented numbering sequences. I haven't been able how to do this all in one table, so I create individual tables for each code to autocrement.


      example Table 1 (parent) is created for my NRT inventory #'s nrt2000, nrt2001 etc to establish a sequence for the user when they set up new equipment.
      Field 1 - Code (3letter code from lookup table - codes)
      Field 2 - Number (autoincremented field)
      Field 3 - Inv_No - Calculated field Code+Number

      Field 3 is posted to child table #2 Master_Eqmt - Inv_No (all my eqmt for each code (NRT, PAR etc) goes to this table). Inv_No in table #2 now sets the basis for a lookup for other tables that need info from master_eqmt (it is in essence my parent table) The user would enter the new eqmt info in the table.

      Table 3 is a Date table and child to Master_Eqmt. It stores the activation and removal dates of each piece of eqmt and posts those dates back to the Master_Eqmt table. It's link field is Inv_No. When my end user wants to remove eqmt, they use Inv_No in table 3 to lookup table 2 Inv_No which will display the any Inventory # and corresponding Activation Date and Removal Date in the lookup window. Posting the Inv_No to this table is where my problem started. I have changed the posting rule for this table to come directly from table 1 instead now since all my tables have a 1 to 1 relation.

      My forms are all created from a set
      Parent - NRT_no Linked by Inv_No with 1to1 relation to
      Child - Master_Eqmt Linked by Inv_no with 1to1 relation to
      GrandChild - NRT_date Linked by Inv_no with 1to1 relation

      I'm in the process of adding a second code sequence in to see if any conflicts are going to arise anywhere else. It seems like a lot of work and repititon but I'm hoping I'm on the right track.

      I'm still pretty new to this but I like what I have accomplished so far in my master database, but from your expert opinion am I on track with my thinking or this in an awkward way of doing things. Is there any easier way of creating this sequence?? I've tried different scenarios over the last week in my test database and this one seems to be the only one I can make work so far.

      Wracking by brains for the best way to do this. :0)

      Thanks so much

      Sue

      Comment

      Working...
      X