Andy Lacey
andy at minstersystems.co.uk
Fri Nov 9 12:48:00 CST 2007
What you might want to do Rocky is set the form's recordsource to something
wich returns no records, eg WHERE Keyfield=-1. Then you can manipulate the
Recordsource when you want to select record or move back and forth, knowing
that initially you'll get no records.
-- Andy Lacey
http://www.minstersystems.co.uk
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Rocky Smolin at Beach Access Software
> Sent: 09 November 2007 18:36
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] JIT Forms
>
>
> So then you can't be opening the form with the record source
> set, yes? Because it's likely to execute before you put the
> filter in the filter in the ClientID field. So are you
> setting the Record Source after putting the filter into ClientID?
>
> And, if so, what's the advantage of just modifying the Record
> Source in the open (or maybe load?) event and adding the
> WHERE clause based on the record ID that you want to fetch?
>
> Rocky
>
>
>
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Friday, November 09, 2007 10:16 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] JIT Forms
>
> I think so. What I do is set one of my
>
> fltr "ClientID", someClientID
>
> and then place fltr("ClientID") in the ClientID field (where)
> of the source query for the form to cause the form to filter
> down to a single record.
>
>
> 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
> Rocky Smolin at Beach Access Software
> Sent: Friday, November 09, 2007 12:56 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] JIT Forms
>
> Unfortunately, in my case. MOST of the bound fields are not
> in subforms but scattered throughout the multiple tabs.
>
> I think we're going for the one record or very few records
> approach by modifying the Record Source on the fly rather
> than using form filters as it is now. Hopefully that reduces
> what's coming over the wire.
>
> Brings up another question - if a filter is set on Open, do
> all the records come over anyway and access just makes the
> filtered subset available to the form?
>
> Rocky
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.503 / Virus Database: 269.15.26/1119 - Release
> Date: 11/8/2007 5:55 PM
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>