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

Updating field in parent table

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

    Updating field in parent table

    I am creating a database to schedule fire inspections for our Department. In the parent table (property information) there is a date field for the scheduled inspection date and a shift field (N2) for the shift which is to perform the inspection. Is there a way to create a link so when the inspection is completed and an entry made in the "inspection" table which is a child to the property info, to update these fields - the date should be advanced by one year, the shift advanced to the next shift (i.e., from "1" to "2", "2" to "3", and "3" back to "1". Can this be done when the monthly report is printed?

    Bill Ruting
    La Grange, IL, Fire Department

    #2
    RE: Updating field in parent table

    Bill,

    You need to open the property table, find the appropriate record, change the date to current date plus a year and close the parent table.

    However there are issues which will crop up:
    -what if one year later falls on a Sunday?
    -do you always reschedule the next inspection when saving the last one?

    I would consider not making the change totally automatic by attaching the script to the inspection table's on save event or some such. Instead I might provide a button to reschedule the inspection forward a year. The code could check for a Sunday or Saturday and advance the next date by 1 or 2 days respectively.

    If you post an example with your actual table and field names I and many others could provide more detailed help.

    Bill
    Bill Hanigsberg

    Comment


      #3
      RE: Updating field in parent table

      Bill - thanks. Actually, the date for the new inspection will be shown only as a MM/YYYY - the inspection is scheduled by the inspector anytime during that month.

      What I am trying now is to import the scheduled month/year from the parent table into the inspection record, then define a calculated field which will add 365 days to that date, then store that date back in the parent table. See if that will work!

      Thanks again,
      Bill

      Comment


        #4
        RE: Updating field in parent table

        That simplifies matters.

        Your design works but let me propose another approach if only for theoretical consideration.

        If the date of the current inspection (in the inspection table) was stored in a date type field, then you would have a variety of functions designed for date manipulation at your disposal:
        -addyears
        -addmonths
        etc.

        At least you should check these out so you know they exist.

        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: Updating field in parent table

          Bill -

          I ended up using the posting properties - first, I imported the current inspection due date into the child table. The fact that an initial inspection record is created satisfies the need for an initial inspection to be done before the date is advanced. In addition, some properties are inspected more than once each year. So, I added a value equal to 365.25 divided by the number of inspections, and added that value to the due date for the current record. The resulting value is then posted to the parent table using the "replace" function. This appears to work well.

          After years of struggling with RBase, Paradox and Access, Alpha 5 is a real breeze!

          Comment

          Working...
          X