[AccessD] AccessD Digest, Vol 47, Issue 40

...so put them all on a 2002 runtime ...99.9999% of those with a full Access 
install are an accident waiting to happen ...and 99.99989% won't know the 
difference anyway if you do your job.

William Hindman

----- Original Message ----- 
From: "JWColby" <jwcolby at colbyconsulting.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Wednesday, January 24, 2007 2:38 PM
Subject: Re: [AccessD] AccessD Digest, Vol 47, Issue 40


> Ken,
>
>>provided the client has Access 2002 or later.
>
> And therein lies the rub.  The specific client with the hugely complex app
> has a mixture of mostly A2K and a handful of AXP (2K2).
>
> 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 Ken Ismert
> Sent: Wednesday, January 24, 2007 1:54 PM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] AccessD Digest, Vol 47, Issue 40
>
> John,
>
> I should read my own article: this works for Access 2002 and later.
>
> Basically, you open an ADO recordset, then disconnect it (Google "ado
> disconnected recordset" for instant code examples).
>
> Then, in your form code, set the combo Recordset property to your
> disconnected recordset:
>
> Set Combo.Recordset = rst
>
> Should be a snap for you to integrate something like this into your
> framework -- provided the client has Access 2002 or later.
>
> -Ken
>
> --
> 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
>