MS access: different layouts for each generated page in Report

[Wesselcram]

I found so many useful answers through other questions, many thanks for that. But now I have a specific question which I yet could not found the answer to. Hopefully any of you can help me..

I have an access table stored with information of different people. Each person has his own ‘personID’. To print that information i need 1 page per person. So I made a report grouped based on the ‘PersonID’ and inserted a pagebreak after that section. It worked perfectly untill I needed to customize the layout of each page based on other information of the table.

For example; I want the textbox’s for person1 on the form to be put closer to each other than for person 2.

Does anyone know the answer to this problem? I use VBA to control the layout of the report which worked perfectly, but i don’t know how to control the layout with VBA for each specific page.

Please let me know if you need any additional information.

Many thanks in advance!

Wessel

 

[vbaInet]

To print that information i need 1 page per person. So I made a report grouped based on the ‘PersonID’ and inserted a pagebreak after that section.

Ok, you don't need a Page Break here. You can Group By Person ID on the report itself (not in the record source) and set the Force New Page property of the group's footer section to True that will be equivalent to (and better) than a page break.

For example; I want the textbox’s for person1 on the form to be put closer to each other than for person 2.

Just wonder why you're needing to do this? Perhaps you can expand on the concept.

 

[Wesselcram]

Thanks for replying. I think I mixed up the terminology. The report is already set up with a group's footer section and the Force New Page set to true.

I am programming questionnaires for my product research company. The layout of the questionnaire is basically an empty table formed by empty textboxes. Because every persons has a different order in which he has to evaluate the products, the location and the layout of the empty cells has to be different for each person.

 

[vbaInet]

So how do you determine this positioning and how many different scenarios are there?

Instead of trying to position controls, it might just be easier to hide/supress some where relevant.

 

[Wesselcram]

Thanks for your thoughts. There a quite a few possibilities (100+). Besides I might need to make more adjustments in de future.

I am now working on the following procedure.

For each personsID I:

1 open a blanc report with VBA in designview.
2 programmatically assemble the report.
3 close and save it
4 open it to for printing
5 close it
6 delete everything from it

Loop

What do you think of this method? And do you know a way how to reset report (step 6)?

 

[vbaInet]

Once you save it that's it. It's the same as manually opening a report in design view and saving it.

I don't think it should come to that anyway. I will need to see what you're trying to do.

 

[Wesselcram]

Dear vbaInet,

I managed to open de report in designview and set everything in place.

I did not remove everything. Instead, i hide most of the labels and unhided them when needed.

Anyway it works and thanks for your help.

Wessel

 

[vbaInet]

If you had shown me a test db I would have come up with a better way. But the important thing is you got it working to your satisfaction.

By the way, you don't need to save the report after making the design change, just open for printing then close it without saving. And you do realise that if you deploy this db to your users as a runtime version (i.e. mde or accde) you will not be able to make any design change in code or otherwise.

 

[Wesselcram]

Hi,

No, unfortunatly I did not and I just found out. Also I discovered some other functions of the database which are not working correctly when carried out in accde.

The database is distributed to 2 - 3 users/computers (with a network). Beside that users can change code, how bad is it to use the splitted microsoft access database? Without publishing it to accde.

Thanks in advance.

 

[vbaInet]

No, unfortunatly I did not and I just found out. Also I discovered some other functions of the database which are not working correctly when carried out in accde.

What functions are these?

The database is distributed to 2 - 3 users/computers (with a network). Beside that users can change code, how bad is it to use the splitted microsoft access database? Without publishing it to accde.

They are both the same. One ensures that your code and object design are locked down and the other isn't locked down. You'll also find that with any properly built application you can't get to meddle with the code.

 

[Wesselcram]

Some createsql code doesn't work. Abviously for the same reason as the reports in design view. It might not be the best code written but it works. I think I will choose to not use accde. Since it will costs too much time to rewrite the code.

Thanks again for the information.

 

[vbaInet]

Experts have been using MDEs and ACCDEs for long and not had any issues. I don't think you understand enough about these format to make these conclusions. I would advise you read about it.

You can build SQL strings absolutely fine and code doesn't have to be re-written. Again, read up on the format.