Hi Clive!
I would love to find a present from Santa! As you'll see in my post to Bill I put a bandaid on the problem and do not have the message any more. But I've gotten this dreaded message before and if at all possible want to avoid it in the future so would REALLY appreciate it if another set of eyes or two would look to see if there's more I could do for this databases or input on preventing this is future databases that I'll build.
I have uploaded the old database and the "fixed" one to the 2_Assistance.. File. The directions for creating the error using the first database is in post##102346.
My last post to Bill describes what I see as a potential problem along with a question about how to solve it.
I've kind of gone overboard with warm fuzzies for my helpers here, but my emotional state has gone from down in the dumps to relieved, cared for, hopeful state. You are a part of that--thank you for jumping in!
Connie
--- In MS_Access_Professionals@yahoogroups.com, "Clive" <zctek@...> wrote:
>
> Hi Connie,
>
> Why don't you upload your zipped dbs before Xmas?
> Better give some driving instruction to get the
> dbs in the state that is most likely to cause
> problems.
>
> By the time you get back, you may find that Santa
> has left you a present.
>
> Have a nice holiday and come back refreshed.
>
> Regards, Clive.
>
> --- In MS_Access_Professionals@yahoogroups.com, mrsgoudge <no_reply@> wrote:
> >
> > Jeff,
> >
> > Thanks for your response--I've encountered this problem several times--right before I think I'm "almost done" and have gone back to rework queries, etc. So I've uploaded it to get as much input as I can so that as more data is added the error doesn't crop up again.
> >
> > Your post reminded me that John had me do something similar before. I then took some time and worked on the underlying queries so that they were simpler and didn't use DLookups and was able to delete the working tables. Recently I changed the most complicated form's underlying queries and opening it takes longer--which may be why I'm back to the same problem.
> >
> > I think my case is similar to yours in that there are several forms with subforms that are opened with and at least one has a zillion queries behind it.
> >
> > thanks!
> > Connie
> >
> >
> > --- In MS_Access_Professionals@yahoogroups.com, "jholm35" <jholm35@> wrote:
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi Connie,
> > >
> > > I'm not sure if this will help with your specific problem or not but I have run into the "too many databases" error before and did manage to work around it.
> > >
> > > In my case the error was caused when I tried to open a complex report that had 14 subreports each of which used several nested queries to arrive at it's final data source. Access seemed to have them all open at once which resulted in the error.
> > >
> > > To make it go away I ended up preprocessing most of the data and dumping the results in a temp table. That allowed me to significantly reduce the number of nested queries my subreports used and therefore the number of objects that were open at one time.
> > >
> > > You may just need to take a look at what is open when the error happens and try to reduce that.
> > >
> > > Hope that helps.
> > >
> > > Cheers,
> > >
> > > Jeff
> > >
> > >
> > > --- In MS_Access_Professionals@yahoogroups.com, mrsgoudge <no_reply@> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > The long and short of this is that I'm wondering if anybody would have time to take a gander at my database? (Remembering of course that I started this as a novice so there's a bunch of ... ;-) ).
> > > >
> > > > I'm back to getting the too many databases error.
> > > > --I tried changing the vba from db to dbPerm which is a public variable that someone suggested long ago. No good. Most of the db is back to Dim db and Setting to nothing on exiting except for the few potential offending forms.
> > > > --I've imported it into a blank database.
> > > >
> > > > I have stepped through the code and when I do, I don't get the "too many databases" message but the last form (contacts) is frozen.
> > > >
> > > > The message can be duplicated. When I tried an older database it was the same, so I've just not been using this feature.
> > > >
> > > > As you would probably guess, I'm discouraged. Usually I'm a like a dog with a bone and I won't give up, but right now I have no idea what else to try.
> > > >
> > > > Thanks for your help,
> > > > Connie
> > > >
> > >
> >
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (9) |
Tidak ada komentar:
Posting Komentar