Help with form details

[rmccafferty]

I need a form that looks essentially like the below (ther are more field, but the following should be enough to get the idea). I need a form, not a report, so that the user can check off one field to mark when entries are processed. I need it to be based on a query to pull enough fields

The base table consists of multiple line items to be invoiced. The line items need to be sorted by client name for obvious grouping needs. We do not want to show the cllient name over and over, line after line, just the first line for that client's line items.

I first tried to do it using a subform for the line item details and the main form for client name, date etc that does not need to be repeated. But then I could not mark the form as continuous. How can I do this?

Client1 Date Amt Etc (only line item for client1)

Client2 Date Amt Etc (first line item for client 2)
Date Amt Etc (second line item for client 2)
Date Amt Etc (third line item for client2)

Client (and so on)

I do not know how to not repeat the client name field (and a couple others not to be repeated) without a subform, which has other negative consequences, particularly the inability to use it as a continuous form.

 

[missinglinq]

I do not know how to not repeat the client name field (and a couple others not to be repeated) without a subform, which has other negative consequences, particularly the inability to use it as a continuous form.

Why do you think that the subform cannot be a Continuous View Form?

 

[rmccafferty]

I first put in the subform and then tried to make the primary form Continuous and I got an error message specifically telling me that you cannot make a for continuous if it has subforms.

Then I tried looking it up (I forget if it was in one of my books or on line) and seemed to find confirmation of that little tidbit.

Which still leaves me stuck on how to show a listing of all clients with un-invoiced line items. And show it in a form (not report) and to keep it somewhat clean looking by only repeating line item data, not client data.

 

[missinglinq]

I apologize! I thought you were referring to not being able to set the subform as a Continuous View form!

But I still don't understand your problem, I'm afraid. The normal way of doing this, and it is a very common scenario, is to use a Single View form for the main form and subform for the line items. Explain again why you need the main form to be Continuous.

 

[boblarson]

And actually you can use a subform with a continuous main form. The only caveat is that it needs to be in the form FOOTER (much like the Access 2007 split form) instead of in the details section.

Rich proved that one to me several years ago. Now I admit it isn't perfect, but it does allow you to have a subform while using a main form in continuous view.

 

[rmccafferty]

Maybe I do not understand continuous forms. I thought I needed a continuous form to show multiple sets of records. That is, my query is going to respond with line items for maybe 10 clients.

So if I set it up the body of the form with something like:

Client1 (sitting on a line by itself)
Subform (now showing lineitem fields
Leave a little space and then end of the form

Will it then keep showing client 2 with subform, client 3 with subform, etc, one after another?

 

[rmccafferty]

I guess I have the same question regarding putting the subform in the footer. With I see first client 1 and its subform (line item details), then client 2 and its subform, etc? Or will the user have to keeping pushing something for next record to see successive clients that are returned by the query?

 

[boblarson]

If the subform is in the footer (where it would have to be if you want to use it with the main form as a continuous form) it would change records as you click into each of the records on the continuous main form.