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

Posting a conditional value from 1 table to another

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

    Posting a conditional value from 1 table to another

    Hi, we have a database that consists of a number of tables such as Clients, Billing, Inspections, etc.

    The billing table simply records date, amount and how many months of additional monthly servicing they require.

    As the database is setup now the client form has a field that records their final month inspection date.

    When someone pays for more inspections we have to manually update the field in client table to record when their subscription expires.

    Is there some way for this to be done automagically? So that when we enter 3, 6 or 12 months of additional inspections it updates the field in the client table? I'm sure there is but I just can't seem to get my head around exactly how to make it happen.

    Any advice or suggestions would be very much appreciated.

    Thanks in advance
    Greg

    #2
    Re: Posting a conditional value from 1 table to another

    There are several possible ways to do this but I don't think you've given enough info.

    when we enter 3, 6 or 12 months of additional inspections
    Is this what you do, enter a numeric 3 or 6 or 12 in some field? Do you create a new record for the additional service or do you modify the previous value to indicate the longer period?
    There can be only one.

    Comment


      #3
      Re: Posting a conditional value from 1 table to another

      HI Stan and thanks for taking a look!

      OK well we run a set made up of 5 different tables. The two problem ones are the billing and the client data tables.

      The client data table has a field that stores the date of the last inspection for that particular client.

      The Billing table shows the client ID, payments made with a date of payment, amount and the period of either 3, 6 or 12 additional months. So we can use that figure of 3, 6 or 12 as the basis for the calculation.

      The only area I'm having a problem with is how to get the billing field to update the last inspection field for that client. I'd imagine it will be a post or append function but as I said in my original post I'm just having trouble getting my head around it.

      Thanks again for any suggestions or input.

      Regards
      Greg

      Comment


        #4
        Re: Posting a conditional value from 1 table to another

        Greg, Stan will probably have a better idea, but here are two possibilities to get the ball rolling:

        1) Add fields for the current date of last inspection and the new date of last inspection to the Billing table. Populate the current date of last inspection using a calc field rule to retrieve the field value from the client data table (using a lookup() function). Use a calc field rule in the Billing table to compute the new date of last inspection. The AddMonths() function will come in handy here. Then use a post field rule on the new date of last inspection field to "replace" the date of last inspection field value in the client data table.

        2) Write a custom script in the CanSaveRecord event in field rules for the Billing table that opens a new instance of the client data table, fetch_finds the desired record, computes the new date of last inspection field value and then writes it to the record before closing the client data table.

        The first approach involves the least amount of coding but would store redundant data in the billing table. The second approach doesn't store any redundant data but would involve more coding.

        Comment

        Working...
        X