priority oder of commands

[Jen0dorf]

Hi

created a form with a data sheet view and ran it all ok

then set up a button to call the form via a macro and viewed my datasheet in form view.

After an hour or so of head scratching and trawling google found the option in the macro to change the view to datasheet.

Ok job done but it does raise the question of hierachy

MAcros seem to take precedence over form properties?

Does VBA take precedence over macros?

Can't seem to find an answer on the web?

THanks

Ian

[CJ_London]

macros and vba are basically the same thing - all a macro is is a user interface to create vba code - in much the same way the query window creates sql. Macro's run code interpretively or 'live' whilst vba code can be compiled so it can't be modified and possibly runs faster.

A macro can be specified to start when the db is opened by calling it autoexec (rather than specifying a form), something that is not possible using vba.

both macros and vba are event driven - you cannot have the same event activate both a macro and vba, although one could call the other.

macros/vba only 'take precedence' over form properties if they are run perhaps on a form open or load event. However in the case of using say docmd.openform, you can override certain form properties such as the view (datasheet/form/continuous form/edit) and set form filters

[NTC]

the command to open an object has the view property as part of the open command; and as you have discovered this does take precedence over the view property of the object itself.

if you double click to open a report/form object from then navigation pane it will rely on the view property of the object: but if you use a command you can alter that view - - if gives the developer better flexibility to see the same object in differing views if need be.....

[Jen0dorf]

Hi

thanks for the clarification

Ian