[AccessD] Back again....

A.D:

Thank you.  I'll try moving those to the load event and see if it makes a
difference.

Regards,

Rocky
 




 	
	

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of A.D.TEJPAL
Sent: Saturday, March 03, 2007 9:55 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Back again....

Rocky,

    You can try the first subroutine adhScaleForm() turn by turn, in open as
well as load event. If there is no advantage in open event from flickering
or any other point of view, load event should be preferred.

    The other subroutine, TranslateControlForm() appears to use values
derived from various controls. Form's controls get stabilized in the load
event. As such, it would be preferable to place this subroutine in the load
event.

Best wishes,
A.D.Tejpal
---------------

  ----- Original Message -----
  From: Rocky Smolin at Beach Access Software
  To: 'Access Developers discussion and problem solving' 
  Sent: Saturday, March 03, 2007 21:20
  Subject: Re: [AccessD] Back again....


  A.D.:

  What  would the best event be to call the adh routine:

       Call adhScaleForm(Me, 640, 480, 96, 96, rctOriginal)

  How about my routine which translates the form     Call
  TranslateControlForm(Me.Name)?

  Thanks and regards,

  Rocky


  -----Original Message-----
  From: accessd-bounces at databaseadvisors.com
  [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of A.D.TEJPAL
  Sent: Saturday, March 03, 2007 4:25 AM
  To: Access Developers discussion and problem solving
  Subject: Re: [AccessD] Back again....

  Bruce,

      Welcome back!

      During open event, the form is supposed to be still in a state of
flux.
  Preferably, use of this event should be confined to those situations where
it is intended to use the Cancel feature inherent in it. Otherwise,
  everything else can normally be placed either in the load event (for one
  time firing) or activate event for repeated firing (e,g, DoCmd.Restore) as
required.

      DoCmd.GoToRecord action requires the target form to have the focus.
There should not be any problem while using it in load event of a form. For
navigation to a particular record via code executed from an external form,
FindFirst method of form's recordset (not the clone) is found convenient as
it does not need any extra code for synchronizing the bookmark. It has
however to be noted that recordset approach can not take you to new record.
For that, DoCmd.GoToRecord method becomes necessary.

      Each implementation of Filter action on a form at run time forces
  requery as well. This takes the form to first control on first record. If
it
  is desired to move to a particular record (after filter or sort action),
  value of primary key control has to be gathered before hand, to be
  eventually used for navigating to destination record.

  Best wishes,
  A.D.Tejpal
  ---------------
--
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.446 / Virus Database: 268.18.6/709 - Release Date: 3/3/2007
8:12 AM