[AccessD] using ADO to populate combos - was RE: Error3048Cannotopen any more databases

Drew Wutka DWUTKA at Marlow.com
Wed Mar 5 10:11:55 CST 2008


That's not necessary, to write a function for each control.  One of the
arguments of that control is the control itself.

So you could create one function, in a module, that would be your
'global' callback function.  What I would recommend would be to create a
class that would handle recordset objects, and in your callback function
pull the appropriate recordset from that class based on the control
argument that is passed to the callback function.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, March 05, 2008 9:17 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] using ADO to populate combos - was RE:
Error3048Cannotopen any more databases

Long ago I tried using call back functions and the only way I could
figure
out to do it was write a callback for each object.  That just doesn't
work
when you want to implement this easily and automatically system wide -
five
hundred different combos.

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 Drew Wutka
Sent: Wednesday, March 05, 2008 10:06 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] using ADO to populate combos - was RE: Error
3048Cannotopen any more databases

Use a callback function.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, March 05, 2008 8:23 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] using ADO to populate combos - was RE: Error 3048
Cannotopen any more databases

I was under the perhaps naive belief that with Access 2000 and greater,
a
combo could be populated by an ADO recordset, i.e. it's rowsource
property
could be an ado recordset.  When I go out and look, I am running into
methods that build up a string and the row source type is set to value
list.
That is a rather useless solution in the majority of cases since the max
limit of characters in the list is around 2000.

Is it in fact possible to make the rowsource an ADO recordset or am I
delusional?  If possible, how is it done?  Example code would be nice. 


John W. Colby
Colby Consulting
www.ColbyConsulting.com 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com The information contained in
this
transmission is intended only for the person or entity to which it is
addressed and may contain II-VI Proprietary and/or II-VI Business
Sensitive
material. If you are not the intended recipient, please contact the
sender
immediately and destroy the material in its entirety, whether electronic
or
hard copy. You are notified that any review, retransmission, copying,
disclosure, dissemination, or other use of, or taking of any action in
reliance upon this information by persons or entities other than the
intended recipient is prohibited.


-- 
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
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.





More information about the AccessD mailing list