macro call

[Jim Hill]

Hello,
%access_exe% %prog_db% /x %macro_name% /excl /nostartup
this is a command prompt command and it opens access and
calls the function over the macro but stays at the first
line in the function. If I say go, it continues and exit.
Any Idea why does it stop in the function?
Thanks,
Jim

 

[Pat Garard]

You don't show us the first few lines of the Macro!
Does the following apply?
Quoted from Access Help:
a.. To run a Visual Basic for Applications procedure when you open a
database, use the
_RunCode_ action in the AutoExec macro or in the macro that you run by
using the
command-line option /x. You can also run a Visual Basic procedure when you
open
a database by creating a form with a Visual Basic procedure defined for its
OnOpen
event. Designate this form as the startup form by right-clicking the
Database window,
clicking Startup, and then entering that form in the Display Form/Page box.
(My _underline_ - you can call a Macro from the command line, but not a
Function)
--
Hope this helps!

Pat Garard
Australia
apgarardATbigpondDOTnetDOTau

"One look is worth a thousand rumours."
Wen Hou, Warring States Period.

"Look twice!"
Pat Garard, 2003.

 

[Van T. Dinh]

Sometimes a breakpoint you used during the debugging process becomes
persistent and affect later execution of the code. Open the function code
in design view, type some dummy blank lines (so that you can compile the
code again). Use the Debug Menu to Clear All Break Points. Compile and
save the code.

Hopefully, thiswill get rid of the persistent break point.

HTH
Van T. Dinh
MVP (Access)