Report Problem with Split Database

[HeyMoe]

Does anyone know of any problems with Access2003 creating reports in a split database?!
To help with the load time of a medium sized database, I recently split it in two.
When a user now runs one of the reports, an error message appears stating "Cannot open anymore databases". (There are no other databases open!) The report in question has a subreport included in it.
When the same report is run in the non-split version, the error does not appear.
It appears that having a subreport within a report in a split database doesn't work!
Any ideas?

Thanks.

 

[boblarson]

Are you on Office 2003 Service Pack 3, by chance?

 

[HeyMoe]

Are you on Office 2003 Service Pack 3, by chance?

SP2 actually.
For why do you ask!?

 

[boblarson]

There have been major problems with SP3, so make sure you don't install. As for your problem and NOT being on SP3, depending on your code you could be opening connections to the backends by code and then that will contribute to the "number of databases opened." That will include opening ADO or DAO recordsets and not using the linked tables, but another connection object. It can also happen if you try to use a connection other than CurrentProject.Db (ADO) or CurrentDb (DAO).

 

[HeyMoe]

There have been major problems with SP3, so make sure you don't install. As for your problem and NOT being on SP3, depending on your code you could be opening connections to the backends by code and then that will contribute to the "number of databases opened." That will include opening ADO or DAO recordsets and not using the linked tables, but another connection object. It can also happen if you try to use a connection other than CurrentProject.Db (ADO) or CurrentDb (DAO).

The report and subreport do not have any code involved.
The RecordSource for both are just queries.
Both queries are OK.