[AccessD] Array as source for query

I sent an application to Jim offlist.  He's poking and prodding it right
now, maybe he can toss some ideas out here... ;)

Drew

-----Original Message-----
From: JWColby [mailto:jwcolby at colbyconsulting.com] 
Sent: Tuesday, January 23, 2007 10:54 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Array as source for query

Jurgen,

I too have bound forms so complex that I get this "no more database"
message.  The surprising thing is that IIRC there are more than 2400
"available" "recordsets".  The issue is (as you have discovered) at LEAST
one is used for each combo, list, form etc.  It turns out that each object
can use two or more "recordsets" as well so it isn't like you can have up to
2400 combos / forms at once.

I too make heavy use of Just In Time subforms, on tabs, connecting and
disconnecting the subforms as the user clicks on and then off of tabs.  That
definitely helps but doesn't solve the problem.  If I can build into my
framework a method of caching the data for combos and then using a callback
that would definitely help.  Combos are about 90% of the problem and this is
an issue that really can cause problems as your forms get complex.

I tried to solve this a few years ago but the cure was as bad as the
problem.  Callback functions are odd ducks, and I was never able to
satisfactorily use a single callback for more than one combo.  It is an
issue I would LOVE to figure out though.

John W. Colby
Colby Consulting
www.ColbyConsulting.com