MS Office Access utility add-in

[Guest]

I converted an Access 97 db to 2003, all seems ok except when trying to
modify the macro's. Office and Access which were purchased and loaded
seperatly.

In trying to use the sendkey function and single stepping through the macro
I get the statement:
Sendkey action requires ms office access utility add-in to be loaded.

Rerun ms Office Access or MS Office setup to reinstall MS Access and MS
Office Access utility add-in.

When I rerun or reinstall I am unable to find the utility to add.

I could use some help
Thanks
Bob

 

[strive4peace]

Hi Bob,

check your library references...

go to the design view of a module (click Modules tab in the
main database window). If you do not have a module, click
the NEW button

then,

Tools, Options

What libraries are checked?

Are any of them marked as "MISSING" ?


Warm Regards,
Crystal
MVP Microsoft Access

remote programming and training
strive4peace2006 at yahoo.com
*
Have an awesome day

 

[Guest]

Whoa, Couldn't sleep last night Crystal??
I'll start out by thanking you for the reply, wasn't sure if my question was
is the right place.

Did you mean, tools; references?
The libraries that are checked under this are:
- Visual Basic for Applications
- MS Access 11.0 Obj. library
- MS DAO 205/305 compatability library
- Utility
- Ole Automation

Looks like the Utility add-in is there but it's not seeing it?

Bob

 

[strive4peace]

Hi Bob,

I was programming all night.

One of the places that SendKeys is (in my version) is in the
Visual Basic library (try removing the utility library)

These are the basic references I have for Access 2000 (don't
know about 2003 since I don't have it installed):

Visual Basic for Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library

If you use DAO, since you had Access 97, the

Microsoft DAO 2.5/3.5 Compatibility Library

which is what you have is a much better source for Help
(throught the Object Browser -- F2 from a module window,
choose DAO from Classes, press F1 on what you want help
with) than the Microsoft DAO 3.6 Object Library that comes
with 2000+

you can preface a command/declaration with the library it
comes from. ie:

VBA.SendKeys "string", true

Warm Regards,
Crystal
MVP Microsoft Access

remote programming and training
strive4peace2006 at yahoo.com
*
Have an awesome day

 

[Douglas J. Steele]

Sorry to argue Crystal, but the appropriate reference for Access 2003 is the
Microsoft DAO 3.6 Object Library, not Microsoft DAO 2.5/3.5 Compatibility
Library. The Compatibility Library is intended for backwards compability for
applications that were developed in Access 2.0

 

[strive4peace]

Hi Doug,

Yes, I realize that ... but for development, the 2.5/3.5 DAO
library has more help (which is what I said in my post as
the reason why I like it better). In my experience, I have
never had any problem using it. What I can't figure out is
why Microsoft didn't put the help from that library into the
later version

After I develop, I switch to the 3.6 library since most
others do not have 2.5/3.5 unless they had Access 97. I use
DAO a lot, so this is something I do on almost every project
I work on.

Warm Regards,
Crystal
MVP Microsoft Access

remote programming and training
strive4peace2006 at yahoo.com
*
Have an awesome day

 

[Guest]

Great!
Thank you Crystal,
Removing the Utility Library solved the add-in statement problem.

I now have more questions involving Macro design:
- When opening a Query in design mode is there any way to go directly to
the criteria location in one of the fields w/o stepping to it w/sendkeys?
- In Office 97 Macro design, sendkeys allowed more than on keystroke to
be added in the statement. Now each statement can only have on keystroke in
it?
- When using the Runmacro statement to go to subroutine, a repeat count
can be set to limit the number of times the routine can be called. So far
this has not been a function that I can get to work. Where can I find more
information on this subject?

Thanks again for your help

Bob

 

[strive4peace]

You're welcome, Bob

What are you trying to do? Change the criteria in your query?

If you use VBA instead of macros, you will have a lot more
flexibility to do what you want in a much better way than
using SendKeys. It is easy to convert macro actions to VBA

for instance, if you have a macro that uses
OpenForm

the VBA code would be

DoCmd.OpenForm "formname", etc if you have more parameters

You can convert any macro command to code using

DoCmd.macroaction


Warm Regards,
Crystal
MVP Microsoft Access

remote programming and training
strive4peace2006 at yahoo.com
*
Have an awesome day

 

[Guest]

Well I guess I'm agonna have to larn me some new stuff.
Sorry, I'm tooo old for this.

Started with computers in the Airforce way back when there were only analog
puters. Worked my way up through the Intel 4004's on up and hand programmed
proms and E-proms in machine language.

Been learning to this point, was hoping the software would carry me through.
You have to realize that after a certain amount of info is stuffed into a
given space, some of it gets written over and or purged on a regular basis.

So back to the problem, I will study up on VBA coding, figured this was
inevitable.

Thanks soo much for your help Crystal. As the Schwartsman said "I'll be back"

Bob

 

[strive4peace]

Hi Bob,

If you email me, I will send you the first 3 chapters of a
book I am writing on programming with VBA

Warm Regards,
Crystal
MVP Microsoft Access

remote programming and training
strive4peace2006 at yahoo.com
*
Have an awesome day