Re: Macro prompt

OOps forgot one thing. Why running VBE? I'm originally intending to write
this utilizing ADO so I will need to use the VB editor for testing purposes.
I may need to made modifications later in case the project specs change.

pcman wrote:
Steve:

Sorry I was pulled away on other projects. To answer your questions:

The cursor was in the sub area being tested. When I attempt to compile the
project either using the menu command or icon both are grayed out. In the
options pop-up menu the the "Compile" section has already checked off Compile
On Demand and Background Compile checked off. When clicking on Run>Run
Sub>UserForm (F5) the Macros menu pops up.

I started a new project for testing purposes. I created very simple one just
have two text boxes and three command buttons (next rec, previous rec, quit --
to end the program). I created the whole project using the wizard. However,
again when I run this newly created project I have the the prompt coming up
asking for the macro to run. I uninstalled the whole MS Office program and
reinstalled it thinking that whatever was in there would be gone. But this
did not materialize as I would have hoped. In my Available References I have:

Visual Basic for Applications
Microsoft Access 11.0 Objet Library
OLE Automation
Microsoft DAO 3.6 Objet Library
Microsoft ActiveX data Objects 2.1 Library
(All of the above is for this testing program only)

Where do I go from here? Thanks.

Pcman,

[quoted text clipped - 11 lines]
grayed out. Also another piece of info, this version of Access is still
using SP1. Thanks.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-macros/200706/1

.