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

Printing Transactions on save ??

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

    Printing Transactions on save ??

    Hi again :)

    Progressing along fine here but have run into a snag.

    When we enter a transaction (set with transactions, clients and stock) we need the system to print a summary that the customer can then sign on pickup of the goods.

    What would be the easiest way to get the transaction to be printed when the record is saved?

    The printout doesn't need to be anything fancy just something that shows the clients name, date, item traded in and item taken in exchange.

    Any info would be helpful and as always thanks in advance! :)

    #2
    RE: Printing Transactions on save ??


    Themis,

    I can imagine two alternative approaches:

    1) The script that saves the record, prints a report, or pops up a simple form, and you print that one form...

    or

    2) You store the necessary information in a separate table, and use that table to print one report at the end of the day, beginning each transaction on a separate page.

    -- tom

    Comment


      #3
      RE: Printing Transactions on save ??

      Hi Tom, good to talk to you again!

      The problem we have is that each transaction, by law here in Australia, requires us to get a signed statement from the client that he is in fact the owner of the goods being traded in.

      This is part of a crackdown on the trading of second hand goods and in turn the sale of stolen property.

      While all the details, ie client name, address, ID, description of goods, etc is available from the database, we have to find some way to get the client to sign the transaction notice. Obviously some way of doing this thru the system would be preferable to manually writing out each transaction.

      At this stage we could in fact do this by doing a print screen (if a print sceen can be done from within A5) when the transaction is finalised as this would have all the info on the screen and we could lay out the form in such a manner as to print the way we require it.

      I'll have another look thru the documentation and see if I can get a handle on what you're suggesting.

      As always, thanks for your input, it's much appreciated.

      Comment


        #4
        RE: Printing Transactions on save ??

        Hi,

        Having been a student of Tom Cone's for a few years (even thought from afar), I remember that he discourages printing forms, so I would make a report based on the set, and using the field rules, on the OnSaveRecord event, and again on the OnChangeRecord event, to force the form to print, and then put up a dialog box asking if the form printed correctly. If so, fine, but if not, print again.

        Hope this helps.

        Regards,
        Jay Talbott
        Jay Talbott
        Lexington, KY

        Comment


          #5
          RE: Printing Transactions on save ??

          Hmmm,,, an interesting dilemma here! I have managed to get the system to print the form with the transaction, the only problem is that insists on printing every stock item in the database on the item traded out!

          Get the client details, item traded in ok but when it gets to the item the client took it prints a report that is some 200 pages long!

          Am I missing something here? Help please :(

          Comment


            #6
            RE: Printing Transactions on save ??

            How are you selecting the Items a client took?

            Are you displaying a browse of the inventory file?

            You may be better off building a "transaction out" table that would contain the client# and the items taken.

            From there, print a report based on a set containing the client, Items-in, and items out as stated above.

            client
            ||=====>items_in
            ||=====>items_out

            then your report can look like an invoice showing all items in and out.

            The advantage is that you would have a history file of all items in, where they are from, and also a history of all items out and who they went to.

            Tom

            Comment


              #7
              RE: Printing Transactions on save ??

              Hi Tom, well I've made some progress and am getting the last record printed out ok by simply pressing a button when the transaction is finished.

              The problem is that the output is a print of the default form! ideally I'd like to be able to layout the form that is being printed in a fashion that only takes up a few lines rather than a whole page with fields down the left hand column.

              This is what appears in the xbasic action area of the button:

              dim A_FORM_CURRENT as c

              range.flags = RANGE_INDEX .or. RANGE_FIRST .or. RANGE_LAST
              range.index_handle = index_record_get(db_current())
              range.filter = ""
              range_add(db_current(), recno(), recno())
              dim A_FORM_CURRENT as c

              preview:
              preview_form(A_FORM_CURRENT)
              goto cleanup

              cleanup:
              range_drop(db_current())
              end

              Any ideas of how I can either edit the default form to a more friendly style or alternatively how to get it to use another form when printing. Any info would be helpful :)

              Comment

              Working...
              X