[AccessD] Error 3048 Cannot open any more databases

jwcolby jwcolby at colbyconsulting.com
Tue Mar 4 21:51:09 CST 2008


Access 2000 cannot bind to updateable ADO recordsets.   


John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
Sent: Tuesday, March 04, 2008 10:32 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error 3048 Cannot open any more databases



aaaah, just to make things exciting this place currently uses Office 2000,
so I am not sure if your suggestion is meaningful or not ("using Access XP
or above" would suggest it is not going to help :-/).

Today the network has been fast and the tool has worked without error (so
far), yesterday network was sluggy and it got corrupt a couple of times.  I
think the sooner I get the back end ported to SQL Server the better.

Thanks once again for the responses. always appreciated.

regards
Darryl


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of jwcolby
Sent: Wednesday, 5 March 2008 2:20 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Error 3048 Cannot open any more databases


Yup!

If you are using Access XP or above, look at binding all combos and lists to
disconnected ADO recordsets.  That will help immensely all by itself.  After
that you will probably need to dive into the dark arts of ADO disconnected
recordsets for the form as well.  As Charlotte said, WANS are considered a
no-no for bound forms in Access.

John W. Colby
Colby Consulting
www.ColbyConsulting.com
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Tuesday, March 04, 2008 8:08 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error 3048 Cannot open any more databases

Darryl,

This is a highly misleading message, because it really means you have too
many connections open.  If you are doing things like populating combo boxes
with select statements, each one of them is opening a connection.  As I
recall, lookups in your tables could do that as well.
Access was NOT meant for WAN use, and to make it even marginally reliable in
that context, you have to rewrite the UI to eliminate any unnecessary
connections to the back end and use a JIT approach to populating lists,
forms, subforms, etc.  There have been previous discussions on this in the
list, so you might take a stroll through the archives and see what you find.

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
Sent: Tuesday, March 04, 2008 4:23 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Error 3048 Cannot open any more databases



Hey folks,

Sorry to bug you with this, Having a lot of, ummm, 'fun' with this database
I am building. Stand alone, it works great, with 5 or so users it works
great, over a WAN with multi users it gets very wobbly and corrupts easily.


Decided that it has to be split into FE and BE, which I have done manually
and linked up the tables. When the DB opens it populates a listbox with
choices for the user as before fine.  However when the users selects an
option which opens the data-entry form (and associated
subforms) I get this lovely error

"Error 3048 Cannot open any more databases"

on this line
sSQL = "SELECT * FROM tbl_FYP_APLID WHERE (((FYPID)=" & lFYPID & ") AND
((tbl_FYP_APLID.APLID)=" & lAPLID & "));"
[Forms]![frm_FYP_APLID].RecordSource = sSQL

Now I know clearly that I must have too "many databases open", but exactly
what the hell does that mean? how did it happen and how can I either 1:
increase the amount of DB's I can have open, or close down some of the
offending databases?

The only clue I have found online is if you don't SET your delcared
CurrentDB to NOTHING when you are done with it, But the code in this
workbook doesn't work like that at all and the modules that do use SET
current DB, does set them to nothing when finished.  Most confusing.

Can anyone shed some light on this. Sorry about all the questions - working
under lot of pressure and learning on the fly.  Educational for sure, but I
am getting through more and more scotch in the evening!!

:) Darryl.


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

This email and any attachments may contain privileged and confidential
information and are intended for the named addressee only. If you have
received this e-mail in error, please notify the sender and delete this
e-mail immediately. Any confidentiality, privilege or copyright is not
waived or lost because this e-mail has been sent to you in error. It is your
responsibility to check this e-mail and any attachments for viruses.  No
warranty is made that this material is free from computer virus or any other
defect or error.  Any loss/damage incurred by using this material is not the
sender's responsibility.  The sender's entire liability will be limited to
resupplying the material.

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list