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

Cartnell re: marking printed records

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

  • Cartnell re: marking printed records

    In the update topic 8/01 your response included:
    I use filters and operations to mark records that have been printed and record the date of the printing.

    I believe the forms that hold the buttons that activate the operation are attached to a table that does not have the printing records.

    #1. Could you post an example of the operations you use to mark records that have been printed. I have just come up against a situation such as this.

    #2. I don't understand your second statement - a form holds a button which is attached to a table....does the table NOT have the printing records?
    I guess its too many clauses in this structure...but I can't make sense of it.
    Rose Weir
    Hanover, Ont

  • #2
    RE: Cartnell re: marking printed records

    1. In my case I'm printing bills and I wanted to know how many times I'd printed and sent a bill, the date it was printed and the first time it was printed. The report filter is:

    TRANSALE>0.001.AND.Totalbalance>0.001.AND.Bill_Now=.t. (this selects the bills that should be printed)

    Then create an update operation with a filter that selects the same records. In this case:

    TRANSALE>0.001.AND.Totalbalance>0.001.AND.Bill_Now=.t.

    Then define the update operation as:


    Billed_times is updated to Billed_times+1
    Date_billed is updated to date()
    First_biled is updated to date() with the condition isblank("First_billed")
    where Billed_times and Date_billed and First_billed are fields in the table being printed.

    2. You're right about this statement. Hard to decipher. What I meant was the form that contains the button that starts the report printing and runs the operation should not be based on the table being printed or updated. I'm not 100% sure this is a necessary precaution and I hope someone else will jump in and set me straight if I'm wrong.

    Comment


    • #3
      RE: Cartnell re: marking printed records

      Ohlen,

      I'm not sure if there is another implication somewhere that I'm missing but I don't see any reason that a print button would need to be placed on a form that is based on a different table. Example - It is quite common to print an address list from a button on the address form.

      As far as updating the same table with print dates goes, I think the same thing would apply. I would usually do an update like this in Xbasic using a file pointer (i.e., fp=table.open("tablename")) so the system can take care of aliases that might be needed when opening a second copy of the table. I have two applications that do this and I'm sure the current form uses the same tables that are being printed and updated. I don't know what would happen if some type of saved update were to be used.

      Cal

      Comment


      • #4
        RE: Cartnell re: marking printed records

        Cql,
        Thanks. I wasn't too sure the precaution was necessary. Appreciate your jumping in.
        Ohlen

        Comment

        Working...
        X