Report Printing And Error 3048

Topic

New Reply

I have a very complex report that has been functioning perfectly for years for several different clients. One I am just finishing up a job for showed me this strange error message (Error 3048 Can’t open any more databases) they were getting which – typical for Microsoft – wasn’t being very helpful. They upshot for them, is they can’t print this report completely. The last two subreports get left off. There are about 8 or 9 subreports and each uses several queries to produce the needed statistic. Many of the queries are crosstabs.

All I can think of is that they are the only client who are using both Office 2007 and running it on Vista. This particular report has not been altered at all and the client running it on XP has no problem.

I’ve read in various forums about writing some data to temp tables, etc, but I’m thinking that perhaps the simplest solution is to just split this two page report into two separate reports. I don’t really have the time or inclination to start fussing with something that used to work just fine.

Any comments or suggestions would be most appreciated.

Reply | Quote

Replies

I have a very complex report that has been functioning perfectly for years for several different clients. One I am just finishing up a job for showed me this strange error message (Error 3048 Can’t open any more databases) they were getting which – typical for Microsoft – wasn’t being very helpful. They upshot for them, is they can’t print this report completely. The last two subreports get left off. There are about 8 or 9 subreports and each uses several queries to produce the needed statistic. Many of the queries are crosstabs.

All I can think of is that they are the only client who are using both Office 2007 and running it on Vista. This particular report has not been altered at all and the client running it on XP has no problem.

I’ve read in various forums about writing some data to temp tables, etc, but I’m thinking that perhaps the simplest solution is to just split this two page report into two separate reports. I don’t really have the time or inclination to start fussing with something that used to work just fine.

Any comments or suggestions would be most appreciated.

It looks like it has somehow hit the maximum 255 concurrent connections that the Access Jet Engine permits.
I don’t know if this is still the limit in 2007, but I suspect it is since it is a Jet limitation.

Luckily I have never encountered this error, but most of the
bigger databases I work with use SQL Server or MYSQL as the Data Source rather than Access,
and more complex queries are performed on the server.

Reply | Quote