In your report's record source where you select which fields to display, add the dots to the field name, such as: FieldWithDots: [fname] & ".........". Put as many dots in as you want, the text box width should stop displaying too many.
Thanks for the reply. I tried what you said and I get the dots to appear so thanks for that. But now I need to tweak it if possible. The thing is, my text boxes are designed to grow when needed, so I need to be able to tell it to stop at a certain point if my 'description' goes on to a second line but that certain point fluctuates. IE, if you look at the picture above as the example, each line has a different amount of 'description' and then each has a different amount of dots, but yet they are told to stop at a point. Basically I do not know the amount of dots to fill, it should determine that automatically.
Call it padding. This will require a non-proportional font such as Courier. Review: http://support.microsoft.com/kb/210573
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Hi June7,your idea is interesting and I may have use for it at some point, but I found out that it is referred to as "leader dots" and accidentally came across this small example, http://www.lebans.com/leaderdots.htm and the file you can download from that page is called leaderdots.zip. Now I do not understand code or how to place it in a report, such as mine that you already know about, but I managed to kind of fight with the example and get it to do the dots for my table/query. However, the issue I have now is that when the description is long and goes onto a second line, the first column of prices then disappears. The only thing I can think of is that maybe when it goes on the second line that it 'covers' over the price, as in the price box is sitting behind the text box and therefore disappears? I don't know if you or somebody can tell me how to do the dot idea properly as I think I have the issue because I have messed around with the example and that it now doesn't do what it was meant to do. Here is my modded version (attached) of the example for my table/query. And when you look at my version look at Bahamas SG 171 as an example. Thanks.
I looked at Lebans 2-line example, which is the one used in your report, and it doesn't seem to work entirely in his.
Your report won't even open.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Hi June7, sorry for the delay in reply. Not sure why the report does not open for you? I downloaded that file of mine from the link and it still worked for me, but then I'm not sure if you are patient enough, IE it takes a very long time to run the report, even the little file here takes a good few seconds to make on my pc. My 36000 odd database file takes about 9-10 minutes to process on my pc, but then I haven't got the greatest either, Core 2 Due 2.66ghz. Somehow the dots work fine for me which is brilliant. Maybe I accidentally changed something that isn't in his original file? But thanks again for your help. Jon.
PS: Please can this thread be marked as solved. Couldn't quite see an option to mark it. Thanks.
Marked solved - Thread Tools above the first post.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.