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

suppress repeated values on report

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

  • Ton Spies
    replied
    Re: suppress repeated values on report

    Originally posted by MikeC View Post
    Ton,
    If I remember right, null numerics are stored/considered as 0 in dbf....but the display can indicate which is which.
    Hi Mike,

    When you create an empty record the Numfields are not yet used.
    But the value of such a field is the same as a Numfield which value represents the result of this calculation 9+3-12
    Both are zero. So IMHO the display cannot indicate the difference.

    Ton

    Leave a comment:


  • MikeC
    replied
    Re: suppress repeated values on report

    Ton,
    I am not understanding what you want exactly....when you "blank" the text on a form, it will blank the record in the table as well....same if you delete the 0 in the table it will then show up on the form as a blank.

    If I remember right, null numerics are stored/considered as 0 in dbf....but the display can indicate which is which.

    Leave a comment:


  • Ton Spies
    replied
    Re: suppress repeated values on report

    Hi Mike,

    Always nice to see comments, clarity, discussions etc.

    So thanks for that but how can you give that more structure?

    I always use the formattingsyle -see attachement -
    But then an empty and a zero are displayed as ""

    Can you make a distinction between them in display?

    Ton

    Leave a comment:


  • MikeC
    replied
    Re: suppress repeated values on report

    As Ton stated....a lot of posts on this subject.

    But although true that
    Null values are not possible in numeric .dbf fields. They are not supported. So default is zero then.
    you can still have a blank field show up if that is what is wanted by simply setting the numeric field's Text value to "". This can be done in a form or a browse...syntax resembling this---

    topparent:Browse1:Your_numeric_field.Text =""

    Now also what Ton said about this thread being off topic is even more true but felt that a bit more clarity was warranted.

    Leave a comment:


  • Ton Spies
    replied
    Re: suppress repeated values on report

    Originally posted by leufj View Post
    How to put a null value into a numeric field by using xbasic function such as IIF()?
    Fur-Jiang
    The problem of two questions in one thread is mostly confusing.
    One subject is discussed and the other will be ignored/forgotten.
    Or you get a confusing pell-mell discussion caused by two subjects.

    Anyway here's the Xbasic command:
    Code:
    Numfield = iif ("blue" = "green",20,0)
    Numfield is the numeric field and blue=green is the condition.
    20 is the value that Numfield gets if the condition is .T. and
    0 if the condition is .F.

    There has been a lot of discussion about the null as a numeric value one would like to have as fieldvalue.
    Null values are not possible in numeric .dbf fields. They are not supported. So default is zero then.

    Leave a comment:


  • Al Buchholz
    replied
    Re: suppress repeated values on report

    Like Tom Cone said.... groupings

    or an example of exactly what you are trying to do.

    Leave a comment:


  • leufj
    replied
    Re: suppress repeated values on report

    Thanks a lot for the help. But I cannot get the right expression. I used blank_duplicate(padrn, grp >grand) and it shows Result: Type C. But it was reverted to the original expression of "pa -> padrn". What got wrong?

    Leave a comment:


  • Tom Cone Jr
    replied
    Re: suppress repeated values on report

    Repeating values can also happen if the report is based on a one to many set and fields from the parent table are dropped into the detail band of the report layout.

    Fur-Jiang, if you're seeing the number of duplicates matches the number of linked child table records it's likely a simple design change in your layout will fix this. Check the "Designing for one-to-many set" section of the user guide discussion of reports.

    Leave a comment:


  • Tbaker
    replied
    Re: suppress repeated values on report

    See this link to suppress repeated values on report

    http://wiki.alphasoftware.com/BLANK_DUPLICATE+Function

    Tom Baker

    Leave a comment:


  • leufj
    started a topic suppress repeated values on report

    suppress repeated values on report

    How to suppress repeated values on report?
    How to put a null value into a numeric field by using xbasic function such as IIF()?
Working...
X