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

Selecting Primary Index at Report Print TIme

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

    Selecting Primary Index at Report Print TIme

    Thanks for your previous responses to my questions. The help allowed me go carry on and get further on my project. I am still at the bottom of the learning curve, trying to move from A4 to A5.

    I have the following problem.

    Table name - "custmast"
    Indexes named - "customernumber" and "customername"

    From a button on a form, I want to print a report named "customerlist", being sure that the "customername" index is always used. The button runs the following inline basic command, but does not change the index. Whatever happens to be the primary index at the time the button is pushed is the index used for the report.

    The command is set to run at "onpush"

    dim global pindex as p
    custlist=table.open("custmast",FILE_RO_SHARED)
    pindex=custlist.index_get("customername")
    custlist.index_primary_put(pindex)
    preview:
    :Report.preview("customer list")
    goto cleanup
    cleanup:
    end

    I am probably missing something real simple, but I can't figure out what it is. Any suggestions?

    Thanks

    #2
    RE: Selecting Primary Index at Report Print TIme

    Jimmy,

    In report properties you can specify selection and order criteria. This is often the most convenient place to do this. Note that you can check "use current selection of records" (still in report properties) which would allow you to do a query by form to select records and then to easily print that selection.

    Bill
    Bill Hanigsberg

    Comment


      #3
      RE: Selecting Primary Index at Report Print TIme

      Jimmy, my guess is that your form is based on your custmast table, right?

      If so, when your script runs, it 'opens' another instance of the custmast table and to keep things straight Alpha Five gives it another name or alias... Your report can't see the new index order because it's using the current selections for custmast, not custmast1 (or whatever other different name is given when the second instance of the table is opened in the same session...)

      Stated differently, if my guess is right your script is not modifying the index order of the table upon which the form is based. It's opening a second instance of the table, and setting the index order there. The report is based on the custmast table, which is probably the first instance (loaded when your form loads), and that's the one which is not be re-ordered.

      Bill's suggestion is a good one. I sometimes make several copies of the same report, specifying different filter and order expressions in each.

      Alternatively, you could modify your script to change the current index for the table upon which your form is based...
      Do this by changing the line...
      custlist=table.open("custmast",FILE_RO_SHARED)
      To...
      custlist=table.current()

      Of course this assumes that your form is actually based on the custmast table, so that table is the 'current' table when your form opens, if you see what I mean.

      Good luck.

      -- tom

      Comment


        #4
        RE: Selecting Primary Index at Report Print TIme

        I put a form using multistate buttons to select a report, multiple range parameters, etc, with the report selection buttons .hide()/.show() a number of screen indicators for the user, in the Code Archive a while back (Multistate Button Report Selection Form).

        It was an older project, so I can't remember, but it should also have ui_msg to tell the user if range info is missing, ending value is greater than starting value, etc. It also shows how to set up a way to fake "panel lights" and turning them on and off. It will also populate a drop down with range selection data from another table (ordered as you want, based on the form's activate or initiate event - forgot which) and set the report's initial starting and ending dates. The dates can be changed using 3 multistate buttons to set each date part. It allows selection of output (preview / fax) and a 3rd range parameter as well.

        The filling of the drop down (can't remember who initially posted that script) and date selection method using multistate buttons can be used in a number of other ways. Basically I posted the form and script to help someone who was asking about what he could do with multistate buttons. There's about 50,000 of them on the form.

        The final report creation script also provides preview and printing to WinFax using a DDE. A section is roughed in to take advantage of v5's feature allowing you to change the printer with a single commande line at print time so you can update it when v5 comes out. Since email will be added with v5, email can easily be added to the select statement doing the final print.

        Oh yeah. It also sets an index based on which report is chosen.

        Comment

        Working...
        X