[AccessD] Advice on A2010....

Darryl Collins darryl at whittleconsulting.com.au
Wed Dec 14 16:36:08 CST 2011


Aaaah, those are good points.  In the past virtually all my forms are unbound and I rarely used datasheet view - although in my current role I do a lot more.  Mind you in this role performance trumps elegance so it doesn't matter if the form looks a bit scrappy as I, or the immediate team, are the only users.  And we know how to fix it if something goes *splat*.  Thanks for shedding some light onto this.



-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kenneth Ismert
Sent: Thursday, 15 December 2011 7:46 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Advice on A2010....

>
> William Benson:
> If rebuilding the form completely, why doesn't copying the controls to 
> a new form and renaming the form suffice?
>

Because you also have to manually duplicate all of the form properties,
which don't copy over automatically.

For example, if your form allows datasheets, all the column width settings
will be reset to their defaults.

Further, the copy-and-paste approach can mess up subtle things like display
order, so controls that show up on the original won't be visible on the
copy.

Thus, if all you need to do is reset the count, I recommend my method,
because the whole form gets copied, leaving no surprises.

Charlotte Foust:
> You avoid that issue entirely if you name all your controls in the first
> place.
>

Giving controls meaningful names is best practice. But that doesn't reset
the counter.

Try modifying Jim's code to give each control a non-default name before the
next is created. The limit didn't change for me.

-Ken
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com






More information about the AccessD mailing list