Answered by:
HideDuplicates Property in Forms???

Question
-
Hi
In Reports its easy to hide duplicates. But how do I do it in Forms?
Cheers // Peter Forss Stockholm
Monday, July 9, 2018 6:56 AM
Answers
-
That would be very complicated. If you need to hide duplicates, use a report, not a form.
Regards, Hans Vogelaar (http://www.eileenslounge.com)
- Marked as answer by ForssPeterNova Monday, July 9, 2018 7:40 AM
Monday, July 9, 2018 7:22 AM
All replies
-
That would be very complicated. If you need to hide duplicates, use a report, not a form.
Regards, Hans Vogelaar (http://www.eileenslounge.com)
- Marked as answer by ForssPeterNova Monday, July 9, 2018 7:40 AM
Monday, July 9, 2018 7:22 AM -
OK Hans
Thanks for helping.
I already have the Report and hoped there was a way in Forms too.
Cheers // Peter Forss Stockholm
Monday, July 9, 2018 7:40 AM -
In Reports its easy to hide duplicates. But how do I do it in Forms?
Hi Peter,
Could a nested query help? First to select the unique records, and use these ID's to fill the form?
Imb.
Monday, July 9, 2018 9:09 AM -
Hi Imb
Please give me an example.
Cheers // Peter Forss Stockholm
Monday, July 9, 2018 10:44 AM -
Please give me an example.
Hi Peter,
First, I think I misinterpreted your post. I was thinking of hiding duplicate RECORDS, at second thought I realised you probably mean hiding duplicate VALUES in fields.
One application where I was thinking of was comparison of the journal books in a financial administration over the years. The number of journal books may differ over the years, so you must first have all the "unique" journal books that are used in the whole range to display for a good comparison.
To hide duplicate values in a continuous form "could" probably be solved with conditional formatting, but I have never used conditional formatting. For not too large recordsets (say < 100 records) I developped a systematics using dynamical subforms. These subforms can be bound or unbound, whatever is the most appropriate. For unbound controls I defined the methods that the control can behave as an bound control.
With these kind of techniques I can produce report-like forms, that can display even unrelated topics, but still are interactive to the user (zoom in to other topics or display single-record forms or link to related items), in which the hiding of duplicate values is easy.
Perhaps I was a little blind for your problem because of my enthousiasm of the possiblities that this way of working offers …
Imb.
Tuesday, July 10, 2018 10:01 PM -
Hi Imb
This is what happens.
Its data from a brewery Production Plan. The data is linked by Date. So if I have like two fillings or more the same day, all other activities (in this case Additives) will show twice that date. In report I just hide the duplicate. See last pic below.
NormallyAbusyDayDueToPlan Datum To Brew Additives Dryhopping Separator/Filter Filling 2018-08-06
Brew No 43: Add Spindasol to Equinox Wheat
Brew No 41: Ready to fill - Pale Ale 2018-08-06
Brew No 43: Add Spindasol to Equinox Wheat
Brew No 42: Ready to fill - Pale Ale Cheers // Peter Forss Stockholm
Wednesday, July 11, 2018 6:49 AM -
NormallyAbusyDayDueToPlan Datum To Brew Additives Dryhopping Separator/Filter Filling 2018-08-06
Brew No 43: Add Spindasol to Equinox Wheat
Brew No 41: Ready to fill - Pale Ale 2018-08-06
Brew No 43: Add Spindasol to Equinox Wheat
Brew No 42: Ready to fill - Pale Ale Hi Peter,
Depending on the situation I use two different approaches.
For "large" recordsets (> 100 records) I use a continuous form with only one record per "Datum". The Filling control is then unbound and displays some calculated value. This can be the concatenation of all occuring values, or just "multiple". (Double)clicking on the control will show a form with all the subsequent values.
For small recordsets I use a couple of subforms, in which I play around with the placing and the visibility of the controls on the subforms. As an example see the next picture.
Imb
Thursday, July 12, 2018 7:02 AM