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

Query record positioning problem

  • Filter
  • Time
  • Show
Clear All
new posts

  • Query record positioning problem

    I have a relatively simple problem but do not know how to fix it.

    I have a client that runs monthly invoices for their customers. Some are sent by snail mail and others are Emailed. This has been running well until they asked to be able to run them in batches of 100 instead of all at once. The last run was in excess of 400 invoices.

    The process starts by having them enter the invoice date they want to run invoices for. I then create a query for invoices with that date that have an outstanding balance. All new invoices will have the billed amount still outstanding.

    When the invoices were run all at once it was easy. I got the first record and fetched the next after it was printed until they were all printed.

    Now that they want them batched by 100 I have to allow for interruption in the printing process and have to be able to restart. I added the total invoice count and the last printed batch count to the Menu table so I can see where it was if they aborted the total print. I only check this if the total invoice count is in excess of 100. The daily invoices they run will not trigger that coding because they do not have that many daily invoices.

    My problem is how do I point the query table pointer to the appropriate record to resume the printing since this is a queried process??

    Attached is a text portion of the coding with the original fetch_first and fetch_next still there. I will need to remove them once I get the proper coding done.

    As usual thank you all for your input to my problem.

    Attached Files

  • #2
    Re: Query record positioning problem

    I doubt I have much to offer except for a few questions: What is their need for a batch of only 100? Is it so they don't run out of paper? Because you mentioned they want to be able to interrupt the printing process. Why not have your function run the batch set to no more than 100, then end it and let them run it again for the next batch?

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford


    • #3
      Re: Query record positioning problem

      For what it's worth, I would add a field to indicate the invoice printed.
      add .and. invoiceprinted to your current query, and put in a counter to
      force it to stop printing invoices when the counter reaches 100.

      If they stop the run before it reaches 100, the query will still catch all
      the unprinted invoices.
      Gregg Schmidt


      • #4
        Re: Query record positioning problem

        The paper is one problem but as they are printing they fold and put them in envelopes if they are postal and file the copies in the customer folders( yes they keep folders!!!) so the pause gives them time to do this work. The postal prints 2 copies and the Email one to file(even tho I keep a copy as a PDF) and if the Email fails I print a report showing that. It was not a real big problem until the count got over 200.