Alex,

FWIW, Visio does a pretty decent job of reverse engineering an existing database, and doing paging/paper size control in there is one heck of a lot easier.

>This whole thing started because a client of mine is working on a project and somehow the ER diagram got to be kept in MS Access (it started with about a dozen tables, and now it's up to around 50).
>
>The roll of being the librarian in this project crept up on me, so I'm the one in charge of printing out the ER diagram and since it doesn't fit entirely into a 1024x768 access window (from which I capture screen shots), I started toying with the possibility of making that window really large in order to capture it entirely in a single shot (as opposed to having to tile images in a graphics application). I know, we should've used xCase, visual UML, visio, or another tool more suitable for the task, but before we knew it we had a diagram that looked like a spider-web with 50 tables caught in it like flies, so starting over wasn't something either of us was anxious to do. So we all tacitly agreed that having to tile images in a graphics app once a week wasn't such a terrible thing.