Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / July 2005

Tip: Looking for answers? Try searching our database.

debugging code- access/vba cannot find 'macro'

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
bern - 29 Jul 2005 17:21 GMT
the f5 or command in the immediate window pops the dialog to enter the macro
to run... if I create a macro, and a function to call from the macro, where
the function then invokes the sub proc I want to step through, that macro is
still not found.  office access 2003 sp1;  The task is so basic to the IDE
that I am frustrated in not finding any mechanism to start the debug of this
updated code.  It worked OK in excel but was slow; we also needed some
db-record ordering capabilities so I ported it to Access to finish a report.  
It was due, oh, days ago, but this has been holding me up.  any help from the
MSPros - very appreciated.
Dirk Goldgar - 29 Jul 2005 17:30 GMT
> the f5 or command in the immediate window pops the dialog to enter
> the macro to run... if I create a macro, and a function to call from
[quoted text clipped - 6 lines]
> oh, days ago, but this has been holding me up.  any help from the
> MSPros - very appreciated.

More information, please.  Could you post the code that you're actually
trying to debug?  Is it an event procedure, a procedure in a form or
report module, or is it in a standard module?  Does the procedure have
any parameters?

Signature

Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

bern - 29 Jul 2005 17:46 GMT
Just a standard public procedure in a standard module, not a class module, a
report or a form.    
no parameters to the proc.  
rather than trying to run my PC into the ground in an excel vba crunch of
26000+ records, this version of the working excel vba is modifed to run
against the data already imported into access tables.   via complex
comparisons of values, this proc then generates a table of summation data
that I will be reporting over.
thanks

> > the f5 or command in the immediate window pops the dialog to enter
> > the macro to run... if I create a macro, and a function to call from
[quoted text clipped - 11 lines]
> report module, or is it in a standard module?  Does the procedure have
> any parameters?
Dirk Goldgar - 29 Jul 2005 18:07 GMT
> Just a standard public procedure in a standard module, not a class
> module, a report or a form.
[quoted text clipped - 5 lines]
> of summation data that I will be reporting over.
> thanks

So, if you open the module in the VB Editor, click in the procedure so
as to make it the active procedure, and then press F5 (or click Run),
does the Macros dialog still appear?  If so, that is odd behavior.

Signature

Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

bern - 29 Jul 2005 18:42 GMT
exactly so.
I have just reset the Jet4.0 engine sandboxmode to '0' to attempt to see if
that had anything to do with the macros not being found, or the functions/
procs for that matter.

> > Just a standard public procedure in a standard module, not a class
> > module, a report or a form.
[quoted text clipped - 9 lines]
> as to make it the active procedure, and then press F5 (or click Run),
> does the Macros dialog still appear?  If so, that is odd behavior.
Dirk Goldgar - 29 Jul 2005 19:30 GMT
> exactly so.
> I have just reset the Jet4.0 engine sandboxmode to '0' to attempt to
> see if that had anything to do with the macros not being found, or
> the functions/ procs for that matter.

Have you tried explicitly compiling the project (Debug -> Compile) to
see if there's maybe a compile error that is preventing the procedure
from executing?

Signature

Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

bern - 29 Jul 2005 21:21 GMT
yes, it has to compile to step through; the sandbox =3 default of MS Office
was indeed the culprit.  all going well now... I thank you for your diligent
effort- have a great weekend!

> > exactly so.
> > I have just reset the Jet4.0 engine sandboxmode to '0' to attempt to
[quoted text clipped - 4 lines]
> see if there's maybe a compile error that is preventing the procedure
> from executing?
Dirk Goldgar - 29 Jul 2005 21:36 GMT
> yes, it has to compile to step through; the sandbox =3 default of MS
> Office was indeed the culprit.  all going well now... I thank you for
> your diligent effort- have a great weekend!

Seem to me like you found your solution yourself, but it's been my
pleasure to sit here and let you bounce ideas off me.  :-)

Signature

Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.