Item no's to show and not to show

[MikeJfromESVA]

I have a decrepancy report based on a combined query that a has a blank row table in order to give me a few blank rows after the db has spit its contents. The blank rows are filled out in the field with pen & ink. I found the code to make borders around my fields based on the tallest text box. I use for my automatic item no. a control source =1.(cs=1) This works great, but it also automatically numbers my blank rows. The people out in the field want to two or more blank lines for one descrepancy. My table look something like this ub= unbound field

cs=1, ub, ub, bound field, ub,ub,ub,ub,ub,ub.

I have tried change the forecolor of the cs=1 field base on the bound field being null and not null. All this does is make the cs=1 blank for all rows. I have also tried to make cs=1 box visible or not visble based on the bound field being null and not null. All this does is make my blank lines disappear.

All I want is my database items to be numbered and my blank lines to appear and not be numbered.

 

[The_Doc_Man]

Part of your problem is that Access uses what is called a "sparse" paradigm. That is, it is designed to work only on what is present, not on what is absent. I absolutely understand your desire to have a user-friendly, paper report for someone to go out into the field and check off some stuff so you can bring it back and update the stuff that just got checked.

Part of your problem, though, is that you don't have data for the boxes you wanted to display. And there is where Access is going to fight you. When you don't have data, Access doesn't want to show what you don't have.

I am going to suggest something based on experience in fighting the Access paradigm. Change your design SLIGHTLY. (Only needs just a little bit.)

You MUST have something there to trigger a line printout as a resonable action but there is no particular need for it to be visible. Just "detectable."

So if you want to print, say, five detail lines with "nothing" in them just so you can have the form, make five records that each contain one blank in each field you wanted to show up. As long as it is a true SPACE character and not a null field, it isn't EMPTY.

This usually implies that you have to include a prime key that ISN'T part of the printed detail record so that you can have create the extra blank lines for printing purposes. BUT if necessary, you can make the prime key a hidden field that is "behind" an opaque field. It is possible to layer fields on a report so that one is "on top" of the other. If the text box "on top" has a non-transparent background, the field behind it remains invisible even you didn't MARK it as invisible. And that is how you have unique numbers yet don't show them.

Another possibility is to include a sub-report at that point, perhaps in DATASHEET mode, that has the space characters I mentioned earlier. If it happens that the sub-report is an "improper" child of the parent report - i.e. parent and child have no "link" fields - you might be able to force the sub-report to do what you wanted.

Does either explanation make sense to you?