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

Green Lines Report

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

    Green Lines Report

    Moved from A5. I had been using this trick to create green line reports..
    If(INT(mrecno()/2=memrecno()/2,"White on Cyan","")
    It works on and looks good on print preview but the print out is a mess of heavy color on all lines is this Alpha or the printer ?

    JIm

    #2
    Re: Green Lines Report

    Why not try

    If(INT(mrecno()/2=memrecno()/2,"White on Black","")

    or similar to see if you get different results?
    There can be only one.

    Comment


      #3
      Re: Green Lines Report

      Something oddly wrong with this expression:
      If(INT(mrecno()/2=memrecno()/2,"White on Cyan","")

      Did you mean:
      If(INT(mrecno()/2)=memrecno()/2,"White on Cyan","") ?

      And if so, and though not directly responsive to your question, isn't the same as:
      If(mrecno()/2=memrecno()/2,"White on Cyan","")

      which is also the same as:

      If(mrecno()=memrecno(),"White on Cyan","")

      And who is memrecno() anyway? A UDF?
      Last edited by G Gabriel; 01-08-2009, 12:57 PM.

      Comment


        #4
        Re: Green Lines Report

        Gabe,

        What I think he meant was:

        If(INT(mrecno()/2)=mrecno()/2,"White on Cyan","")

        And that is not the same as:

        If(mrecno()/2=mrecno()/2,"White on Cyan","")

        By using the INT() command even results from mrecno() will be true and odd results from mrecno() be false.

        int(4/2) = 2 and (4/2) =2

        int(5/2) = 2 and (5/2) = 2.5
        Jeff Ryder

        Comment


          #5
          Re: Green Lines Report

          You could also do:

          If(mod(mrecno(),2)=0,"White on Cyan","")

          Result will be 0 for even numbers and 1 for odd numbers.
          Jeff Ryder

          Comment


            #6
            Re: Green Lines Report

            Yes Jeff, but:
            int(5/2) will have the same outcome as int(4/2), both will yield 2.
            Which make me believe he is not testing for odd and even but rather something else that has to do with the outcome of a UDF, the memrecno().
            If you are testing for odd and even, you need to use mod() not int().
            Last edited by G Gabriel; 01-09-2009, 04:06 AM.

            Comment


              #7
              Re: Green Lines Report

              Gabe,

              I have used int() for years on a language that did not have a mod() command for determining even/odd and it works just fine.

              Code:
              if int(a/2) = (a/2) then
                   // even code 
                else
                  // odd code
              end if
              Jeff Ryder

              Comment


                #8
                Re: Green Lines Report

                Originally posted by jaryder View Post
                Gabe,

                I have used int() for years on a language that did not have a mod() command for determining even/odd and it works just fine.

                Code:
                if int(a/2) = (a/2) then
                     // even code 
                  else
                    // odd code
                end if
                Nothing wrong with that.

                Comment


                  #9
                  Re: Green Lines Report

                  Originally posted by jaryder View Post
                  Gabe,

                  I have used int() for years on a language that did not have a mod() command for determining even/odd and it works just fine.

                  Code:
                  if int(a/2) = (a/2) then
                       // even code 
                    else
                      // odd code
                  end if
                  Nothing wrong with that except the original question says:
                  INT(mrecno()/2=memrecno()/2
                  Perhaps a typo.

                  Comment


                    #10
                    Re: Green Lines Report

                    Nothing wrong with that except the original question says:
                    INT(mrecno()/2=memrecno()/2
                    Perhaps a typo.
                    Agreed.
                    Jeff Ryder

                    Comment


                      #11
                      Re: Green Lines Report

                      And a nit-picking mathmatician-programmer (not me) will tell you:
                      in an expression like:
                      If (int(mrecno()/2)=mrecno()/2) you are using 2 evaluations, while in:
                      if(mod(mrecno(),2=0) you are using only one!
                      The difference would be just about enough to buy a hot dog or a burger!

                      Comment


                        #12
                        Re: Green Lines Report

                        Yes you guys found the fat thumb typo, Your assumtions on the correct "mrecno" are correct. I know it is not the printer. It printed this perfectly from V5. V9 shows it in the print preview pane absolutely correctly...It just does not print it the way it is displayed. Evidently V9 just does'nt like to print this type of green lines preview. I have tried several different definitions for the expression (none worked)

                        Jim

                        Comment


                          #13
                          Re: Green Lines Report

                          I doubt it's alpha. Most likely the printer. Try a different printer.
                          The expression, lacking the typos, is fine. (I prefer mod for simplicity but tha's not a big deal really).You must have changed printers since it worked last. Also Cyan is a heavy color, you might want to choose a lighter one.

                          Comment


                            #14
                            Re: Green Lines Report

                            Just to finish this up.. The printer I am using is the same printer that I was using on V5. To prove it is V9 I moved a database from V5 to V9 and guess what ? It worked perfectly to my printer. I think it has to do with the way V9 sets up the color types .. i.e. solid, etc.. It gives you no way to set a fill pattern that works.

                            Jim

                            Comment


                              #15
                              Re: Green Lines Report

                              No Green Line Reports Can Be Set Up In V9..however If You Bring The Database From V5 It Is The Only Way To Do It. I Guess I Have To Live With This..not Being Able To Do It In V9

                              Jim

                              Comment

                              Working...
                              X