Halt screen startling inexperienced users

[BJM]

I have a form that is populated by way of a macro that
runs, among other things, a parameter query. The problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and reports as
much in a very user-unfriendly way. Users of the database
panic and come running for advice!

Is there a way I can, like with the macro Set Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM

 

[Ken Snell]

Not directly.

If you want this option, then don't use the built-in "parameter" box
(actually an InputBox). Create your own form that allows the user to enter
the desired value(s) into textbox(es) and then they can click an OK (or Run)
command button, or they can click a Cancel button. You then have each button
run its own code to either run the query (OK) or not run the query (Cancel).
You then change the query so that it uses the form's textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]

 

[Guest]

Think outside the box, so to speak. Brilliant! Yes. Much
more comfortable for users. And thank you for the syntax
for the query criteria.

BJM

-----Original Message-----
Not directly.

If you want this option, then don't use the built- in "parameter" box
(actually an InputBox). Create your own form that allows the user to enter
the desired value(s) into textbox(es) and then they can click an OK (or Run)
command button, or they can click a Cancel button. You then have each button
run its own code to either run the query (OK) or not run the query (Cancel).
You then change the query so that it uses the form's textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

I have a form that is populated by way of a macro that
runs, among other things, a parameter query. The problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and reports as
much in a very user-unfriendly way. Users of the database
panic and come running for advice!

Is there a way I can, like with the macro Set Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM

.

 

[Erin]

Yes, but this won't work if you have Access 2003! The Set
Value action to hide the form while keeping it open for
the queries to access won't work! There are 4 postings
about this problem in this group since Christmas, but no
answers to the problem:

Macro problem macro frustration 1/2/04
Macro action failed 1/14/04
Problem with Macro 1/19/04
Macro errors after 2003 upgrad! 1/19/04 (mine)
(and another of mine from 12/22/03)

Can anyone help?

-----Original Message-----
Not directly.

If you want this option, then don't use the built- in "parameter" box
(actually an InputBox). Create your own form that allows the user to enter
the desired value(s) into textbox(es) and then they can click an OK (or Run)
command button, or they can click a Cancel button. You then have each button
run its own code to either run the query (OK) or not run the query (Cancel).
You then change the query so that it uses the form's textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

I have a form that is populated by way of a macro that
runs, among other things, a parameter query. The problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and reports as
much in a very user-unfriendly way. Users of the database
panic and come running for advice!

Is there a way I can, like with the macro Set Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM

.

 

[Ken Snell]

I have not seen other similar problems with A2003, so perhaps it is related
to your specific code/macro? Can you post more information here about what
you were doing and what isn't working?

--
Ken Snell
<MS ACCESS MVP>

Yes, but this won't work if you have Access 2003! The Set
Value action to hide the form while keeping it open for
the queries to access won't work! There are 4 postings
about this problem in this group since Christmas, but no
answers to the problem:

Macro problem macro frustration 1/2/04
Macro action failed 1/14/04
Problem with Macro 1/19/04
Macro errors after 2003 upgrad! 1/19/04 (mine)
(and another of mine from 12/22/03)

Can anyone help?

-----Original Message-----
Not directly.

If you want this option, then don't use the built- in "parameter" box
(actually an InputBox). Create your own form that allows the user to enter
the desired value(s) into textbox(es) and then they can click an OK (or Run)
command button, or they can click a Cancel button. You then have each button
run its own code to either run the query (OK) or not run the query (Cancel).
You then change the query so that it uses the form's textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

I have a form that is populated by way of a macro that
runs, among other things, a parameter query. The problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and reports as
much in a very user-unfriendly way. Users of the database
panic and come running for advice!

Is there a way I can, like with the macro Set Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM

.

 

[Erin]

Yes, thanks.

I created a db in Access 2000. There are several reports
which are each built upon several parameter queries. I use
a form to ask for the parameter which then supplies the
parameter to all queries and prints the parameter in the
report. On opening the report the macro opens the user
input form, the OK button on the form hides the
form, keeping it open, so the queries can access the
parameter. Closing the report closes the form. This is
straight from Access Help files and is something my users
use daily. It has always worked beautifully.

I upgraded to Access 2003 and now the macro errors at the
SetValue action (Object: my input form, Property:
[Visible] Value: No)that hides the form. I get an error
message stating that "there is an invalid reference to the
property visible. The property may not exist or may not
apply to the object specified." But Access' documentation
says that the visible property does apply to a form.
Sometimes I get the message that I need to register my
Active X control, (I am only using the standard command
button on the form toolbox). So I tried making sure I had
all my needed references set per online help article - I
don't have the article #, but it is titled "References
that you must set when you use Office Access 2003." I am
unable to set any references. I get error message then
that says the "name conflicts with an existing module,
project or library."

I have tried Office Updates and repairing my installation
(as well as swearing and making faces at the monitor).

This should work! Is this a bug with 2003? I can't allow
my company to install the upgrades we already obtained if
the databases won't work after!

Thanks very much for your help.

Erin

-----Original Message-----
I have not seen other similar problems with A2003, so perhaps it is related
to your specific code/macro? Can you post more information here about what
you were doing and what isn't working?

--
Ken Snell
<MS ACCESS MVP>

Yes, but this won't work if you have Access 2003! The Set
Value action to hide the form while keeping it open for
the queries to access won't work! There are 4 postings
about this problem in this group since Christmas, but no
answers to the problem:

Macro problem macro frustration 1/2/04
Macro action failed 1/14/04
Problem with Macro 1/19/04
Macro errors after 2003 upgrad! 1/19/04 (mine)
(and another of mine from 12/22/03)

Can anyone help?

-----Original Message-----
Not directly.

If you want this option, then don't use the built- in "parameter" box
(actually an InputBox). Create your own form that

allows
the user to enter

the desired value(s) into textbox(es) and then they can click an OK (or Run)
command button, or they can click a Cancel button. You then have each button
run its own code to either run the query (OK) or not

run
the query (Cancel).

You then change the query so that it uses the form's textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

I have a form that is populated by way of a macro that
runs, among other things, a parameter query. The problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and reports as
much in a very user-unfriendly way. Users of the database
panic and come running for advice!

Is there a way I can, like with the macro Set Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM


.

.

 

[Ken Snell]

I know of no reason why this wouldn't work for you.

Try using the full reference to the form's visible property in the Item box:
Forms!InputFormName.Form.Visible

And use this in the Expression box:
False

See if that works.

Yes, thanks.

I created a db in Access 2000. There are several reports
which are each built upon several parameter queries. I use
a form to ask for the parameter which then supplies the
parameter to all queries and prints the parameter in the
report. On opening the report the macro opens the user
input form, the OK button on the form hides the
form, keeping it open, so the queries can access the
parameter. Closing the report closes the form. This is
straight from Access Help files and is something my users
use daily. It has always worked beautifully.

I upgraded to Access 2003 and now the macro errors at the
SetValue action (Object: my input form, Property:
[Visible] Value: No)that hides the form. I get an error
message stating that "there is an invalid reference to the
property visible. The property may not exist or may not
apply to the object specified." But Access' documentation
says that the visible property does apply to a form.
Sometimes I get the message that I need to register my
Active X control, (I am only using the standard command
button on the form toolbox). So I tried making sure I had
all my needed references set per online help article - I
don't have the article #, but it is titled "References
that you must set when you use Office Access 2003." I am
unable to set any references. I get error message then
that says the "name conflicts with an existing module,
project or library."

I have tried Office Updates and repairing my installation
(as well as swearing and making faces at the monitor).

This should work! Is this a bug with 2003? I can't allow
my company to install the upgrades we already obtained if
the databases won't work after!

Thanks very much for your help.

Erin

-----Original Message-----
I have not seen other similar problems with A2003, so perhaps it is related
to your specific code/macro? Can you post more information here about what
you were doing and what isn't working?

--
Ken Snell
<MS ACCESS MVP>

Yes, but this won't work if you have Access 2003! The Set
Value action to hide the form while keeping it open for
the queries to access won't work! There are 4 postings
about this problem in this group since Christmas, but no
answers to the problem:

Macro problem macro frustration 1/2/04
Macro action failed 1/14/04
Problem with Macro 1/19/04
Macro errors after 2003 upgrad! 1/19/04 (mine)
(and another of mine from 12/22/03)

Can anyone help?



-----Original Message-----
Not directly.

If you want this option, then don't use the built-
in "parameter" box
(actually an InputBox). Create your own form that allows
the user to enter
the desired value(s) into textbox(es) and then they can
click an OK (or Run)
command button, or they can click a Cancel button. You
then have each button
run its own code to either run the query (OK) or not run
the query (Cancel).
You then change the query so that it uses the form's
textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

message
I have a form that is populated by way of a macro that
runs, among other things, a parameter query. The problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and reports as
much in a very user-unfriendly way. Users of the
database
panic and come running for advice!

Is there a way I can, like with the macro Set Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM


.

.

 

[Erin]

No, it didn't work, but it did change my error message to
always display the one about not having the license
required to display that Active X control (instead of the
usual about visible not being a property of forms).

I checked my references in VBA again. The article I
referenced below says I need Microsoft Active X Data
Objects 2.1 Library Reference and 2.5 Library Reference. I
am only able to have one or the other or I get an error
stating that name conflicts with an existing library. The
macro won't run whichever reference I set.

I can't find any other information at their website that
looks like it would relate to this problem, either.

-----Original Message-----
I know of no reason why this wouldn't work for you.

Try using the full reference to the form's visible property in the Item box:
Forms!InputFormName.Form.Visible

And use this in the Expression box:
False

See if that works.

Yes, thanks.

I created a db in Access 2000. There are several reports
which are each built upon several parameter queries. I use
a form to ask for the parameter which then supplies the
parameter to all queries and prints the parameter in the
report. On opening the report the macro opens the user
input form, the OK button on the form hides the
form, keeping it open, so the queries can access the
parameter. Closing the report closes the form. This is
straight from Access Help files and is something my users
use daily. It has always worked beautifully.

I upgraded to Access 2003 and now the macro errors at the
SetValue action (Object: my input form, Property:
[Visible] Value: No)that hides the form. I get an error
message stating that "there is an invalid reference to the
property visible. The property may not exist or may not
apply to the object specified." But Access' documentation
says that the visible property does apply to a form.
Sometimes I get the message that I need to register my
Active X control, (I am only using the standard command
button on the form toolbox). So I tried making sure I had
all my needed references set per online help article - I
don't have the article #, but it is titled "References
that you must set when you use Office Access 2003." I am
unable to set any references. I get error message then
that says the "name conflicts with an existing module,
project or library."

I have tried Office Updates and repairing my installation
(as well as swearing and making faces at the monitor).

This should work! Is this a bug with 2003? I can't allow
my company to install the upgrades we already obtained if
the databases won't work after!

Thanks very much for your help.

Erin

-----Original Message-----
I have not seen other similar problems with A2003, so perhaps it is related
to your specific code/macro? Can you post more information here about what
you were doing and what isn't working?

--
Ken Snell
<MS ACCESS MVP>

Yes, but this won't work if you have Access 2003! The Set
Value action to hide the form while keeping it open for
the queries to access won't work! There are 4 postings
about this problem in this group since Christmas, but no
answers to the problem:

Macro problem macro frustration 1/2/04
Macro action failed 1/14/04
Problem with Macro 1/19/04
Macro errors after 2003 upgrad! 1/19/04 (mine)
(and another of mine from 12/22/03)

Can anyone help?



-----Original Message-----
Not directly.

If you want this option, then don't use the built-
in "parameter" box
(actually an InputBox). Create your own form that allows
the user to enter
the desired value(s) into textbox(es) and then they can
click an OK (or Run)
command button, or they can click a Cancel button. You
then have each button
run its own code to either run the query (OK) or not run
the query (Cancel).
You then change the query so that it uses the form's
textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

message
I have a form that is populated by way of a macro that
runs, among other things, a parameter query. The problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and reports as
much in a very user-unfriendly way. Users of the
database
panic and come running for advice!

Is there a way I can, like with the macro Set Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM


.



.

.

 

[Douglas J. Steele]

Are you talking about http://support.microsoft.com/?id=825796

It doesn't say you need both references at the same time.

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)

No, it didn't work, but it did change my error message to
always display the one about not having the license
required to display that Active X control (instead of the
usual about visible not being a property of forms).

I checked my references in VBA again. The article I
referenced below says I need Microsoft Active X Data
Objects 2.1 Library Reference and 2.5 Library Reference. I
am only able to have one or the other or I get an error
stating that name conflicts with an existing library. The
macro won't run whichever reference I set.

I can't find any other information at their website that
looks like it would relate to this problem, either.

-----Original Message-----
I know of no reason why this wouldn't work for you.

Try using the full reference to the form's visible property in the Item box:
Forms!InputFormName.Form.Visible

And use this in the Expression box:
False

See if that works.

Yes, thanks.

I created a db in Access 2000. There are several reports
which are each built upon several parameter queries. I use
a form to ask for the parameter which then supplies the
parameter to all queries and prints the parameter in the
report. On opening the report the macro opens the user
input form, the OK button on the form hides the
form, keeping it open, so the queries can access the
parameter. Closing the report closes the form. This is
straight from Access Help files and is something my users
use daily. It has always worked beautifully.

I upgraded to Access 2003 and now the macro errors at the
SetValue action (Object: my input form, Property:
[Visible] Value: No)that hides the form. I get an error
message stating that "there is an invalid reference to the
property visible. The property may not exist or may not
apply to the object specified." But Access' documentation
says that the visible property does apply to a form.
Sometimes I get the message that I need to register my
Active X control, (I am only using the standard command
button on the form toolbox). So I tried making sure I had
all my needed references set per online help article - I
don't have the article #, but it is titled "References
that you must set when you use Office Access 2003." I am
unable to set any references. I get error message then
that says the "name conflicts with an existing module,
project or library."

I have tried Office Updates and repairing my installation
(as well as swearing and making faces at the monitor).

This should work! Is this a bug with 2003? I can't allow
my company to install the upgrades we already obtained if
the databases won't work after!

Thanks very much for your help.

Erin


-----Original Message-----
I have not seen other similar problems with A2003, so
perhaps it is related
to your specific code/macro? Can you post more
information here about what
you were doing and what isn't working?

--
Ken Snell
<MS ACCESS MVP>

message
Yes, but this won't work if you have Access 2003! The
Set
Value action to hide the form while keeping it open for
the queries to access won't work! There are 4 postings
about this problem in this group since Christmas, but no
answers to the problem:

Macro problem macro frustration 1/2/04
Macro action failed 1/14/04
Problem with Macro 1/19/04
Macro errors after 2003 upgrad! 1/19/04 (mine)
(and another of mine from 12/22/03)

Can anyone help?



-----Original Message-----
Not directly.

If you want this option, then don't use the built-
in "parameter" box
(actually an InputBox). Create your own form that
allows
the user to enter
the desired value(s) into textbox(es) and then they can
click an OK (or Run)
command button, or they can click a Cancel button. You
then have each button
run its own code to either run the query (OK) or not
run
the query (Cancel).
You then change the query so that it uses the form's
textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

message
I have a form that is populated by way of a macro
that
runs, among other things, a parameter query. The
problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and
reports as
much in a very user-unfriendly way. Users of the
database
panic and come running for advice!

Is there a way I can, like with the macro Set
Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM


.



.

.

 

[Ken Snell]

Erin -

I found a post on another newsgroup that said the poster had contacted
Microsoft about this and had been told that there is a problem with the
Visible property of a form in a macro's SetValue action. I have not been
able to confirm this yet, but your info seems to match that of the other
poster's.

The workaround is to use VBA code to run that particular macro action. In
place of the SetValue action in your macro, put the RunCode action (we'll
set up a public function in a moment here) and tell the action that the
function argument is MakeFormInvisible() (included the () in the argument):
Action: RunCode
Function: MakeFormInvisible()

Then, go to the database window and click on Modules. Open a new module and
type the following into it:

Public Function MakeFormInvisible()
Forms!InputFormName.Form.Visible = False
End Function

(Replace InputFormName with the actual name of the form.)

Save the module and name it basFunctions.

This should now work for you. I'm still checking on this "bug" possibility.

--
Ken Snell
<MS ACCESS MVP>

No, it didn't work, but it did change my error message to
always display the one about not having the license
required to display that Active X control (instead of the
usual about visible not being a property of forms).

I checked my references in VBA again. The article I
referenced below says I need Microsoft Active X Data
Objects 2.1 Library Reference and 2.5 Library Reference. I
am only able to have one or the other or I get an error
stating that name conflicts with an existing library. The
macro won't run whichever reference I set.

I can't find any other information at their website that
looks like it would relate to this problem, either.

-----Original Message-----
I know of no reason why this wouldn't work for you.

Try using the full reference to the form's visible property in the Item box:
Forms!InputFormName.Form.Visible

And use this in the Expression box:
False

See if that works.

Yes, thanks.

I created a db in Access 2000. There are several reports
which are each built upon several parameter queries. I use
a form to ask for the parameter which then supplies the
parameter to all queries and prints the parameter in the
report. On opening the report the macro opens the user
input form, the OK button on the form hides the
form, keeping it open, so the queries can access the
parameter. Closing the report closes the form. This is
straight from Access Help files and is something my users
use daily. It has always worked beautifully.

I upgraded to Access 2003 and now the macro errors at the
SetValue action (Object: my input form, Property:
[Visible] Value: No)that hides the form. I get an error
message stating that "there is an invalid reference to the
property visible. The property may not exist or may not
apply to the object specified." But Access' documentation
says that the visible property does apply to a form.
Sometimes I get the message that I need to register my
Active X control, (I am only using the standard command
button on the form toolbox). So I tried making sure I had
all my needed references set per online help article - I
don't have the article #, but it is titled "References
that you must set when you use Office Access 2003." I am
unable to set any references. I get error message then
that says the "name conflicts with an existing module,
project or library."

I have tried Office Updates and repairing my installation
(as well as swearing and making faces at the monitor).

This should work! Is this a bug with 2003? I can't allow
my company to install the upgrades we already obtained if
the databases won't work after!

Thanks very much for your help.

Erin


-----Original Message-----
I have not seen other similar problems with A2003, so
perhaps it is related
to your specific code/macro? Can you post more
information here about what
you were doing and what isn't working?

--
Ken Snell
<MS ACCESS MVP>

message
Yes, but this won't work if you have Access 2003! The
Set
Value action to hide the form while keeping it open for
the queries to access won't work! There are 4 postings
about this problem in this group since Christmas, but no
answers to the problem:

Macro problem macro frustration 1/2/04
Macro action failed 1/14/04
Problem with Macro 1/19/04
Macro errors after 2003 upgrad! 1/19/04 (mine)
(and another of mine from 12/22/03)

Can anyone help?



-----Original Message-----
Not directly.

If you want this option, then don't use the built-
in "parameter" box
(actually an InputBox). Create your own form that
allows
the user to enter
the desired value(s) into textbox(es) and then they can
click an OK (or Run)
command button, or they can click a Cancel button. You
then have each button
run its own code to either run the query (OK) or not
run
the query (Cancel).
You then change the query so that it uses the form's
textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

message
I have a form that is populated by way of a macro
that
runs, among other things, a parameter query. The
problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and
reports as
much in a very user-unfriendly way. Users of the
database
panic and come running for advice!

Is there a way I can, like with the macro Set
Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM


.



.

.

 

[Erin]

Success! Thank you very much!
Now it seems such an easy solution it should have been
obvious to me. Thanks again!
Erin

-----Original Message-----
Erin -

I found a post on another newsgroup that said the poster had contacted
Microsoft about this and had been told that there is a problem with the
Visible property of a form in a macro's SetValue action. I have not been
able to confirm this yet, but your info seems to match that of the other
poster's.

The workaround is to use VBA code to run that particular macro action. In
place of the SetValue action in your macro, put the RunCode action (we'll
set up a public function in a moment here) and tell the action that the
function argument is MakeFormInvisible() (included the () in the argument):
Action: RunCode
Function: MakeFormInvisible()

Then, go to the database window and click on Modules. Open a new module and
type the following into it:

Public Function MakeFormInvisible()
Forms!InputFormName.Form.Visible = False
End Function

(Replace InputFormName with the actual name of the form.)

Save the module and name it basFunctions.

This should now work for you. I'm still checking on this "bug" possibility.

--
Ken Snell
<MS ACCESS MVP>

No, it didn't work, but it did change my error message to
always display the one about not having the license
required to display that Active X control (instead of the
usual about visible not being a property of forms).

I checked my references in VBA again. The article I
referenced below says I need Microsoft Active X Data
Objects 2.1 Library Reference and 2.5 Library Reference. I
am only able to have one or the other or I get an error
stating that name conflicts with an existing library. The
macro won't run whichever reference I set.

I can't find any other information at their website that
looks like it would relate to this problem, either.

-----Original Message-----
I know of no reason why this wouldn't work for you.

Try using the full reference to the form's visible property in the Item box:
Forms!InputFormName.Form.Visible

And use this in the Expression box:
False

See if that works.

Yes, thanks.

I created a db in Access 2000. There are several reports
which are each built upon several parameter queries.

I
use

a form to ask for the parameter which then supplies the
parameter to all queries and prints the parameter in the
report. On opening the report the macro opens the user
input form, the OK button on the form hides the
form, keeping it open, so the queries can access the
parameter. Closing the report closes the form. This is
straight from Access Help files and is something my users
use daily. It has always worked beautifully.

I upgraded to Access 2003 and now the macro errors at the
SetValue action (Object: my input form, Property:
[Visible] Value: No)that hides the form. I get an error
message stating that "there is an invalid reference

to
the

property visible. The property may not exist or may not
apply to the object specified." But Access' documentation
says that the visible property does apply to a form.
Sometimes I get the message that I need to register my
Active X control, (I am only using the standard command
button on the form toolbox). So I tried making sure I had
all my needed references set per online help article - I
don't have the article #, but it is titled "References
that you must set when you use Office Access 2003." I am
unable to set any references. I get error message then
that says the "name conflicts with an existing module,
project or library."

I have tried Office Updates and repairing my installation
(as well as swearing and making faces at the monitor).

This should work! Is this a bug with 2003? I can't allow
my company to install the upgrades we already

obtained
if

the databases won't work after!

Thanks very much for your help.

Erin


-----Original Message-----
I have not seen other similar problems with A2003, so
perhaps it is related
to your specific code/macro? Can you post more
information here about what
you were doing and what isn't working?

--
Ken Snell
<MS ACCESS MVP>

message
Yes, but this won't work if you have Access 2003! The
Set
Value action to hide the form while keeping it

open
for

the queries to access won't work! There are 4 postings
about this problem in this group since Christmas, but no
answers to the problem:

Macro problem macro frustration 1/2/04
Macro action failed 1/14/04
Problem with Macro 1/19/04
Macro errors after 2003 upgrad! 1/19/04 (mine)
(and another of mine from 12/22/03)

Can anyone help?



-----Original Message-----
Not directly.

If you want this option, then don't use the built-
in "parameter" box
(actually an InputBox). Create your own form that
allows
the user to enter
the desired value(s) into textbox(es) and then

they
can

click an OK (or Run)
command button, or they can click a Cancel

button.
You

then have each button
run its own code to either run the query (OK) or not
run
the query (Cancel).
You then change the query so that it uses the form's
textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

message
I have a form that is populated by way of a macro
that
runs, among other things, a parameter query. The
problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and
reports as
much in a very user-unfriendly way. Users of the
database
panic and come running for advice!

Is there a way I can, like with the macro Set
Warnings
setting, turn this off and have the macro just halt
quietly!?!

Thanks,
BJM


.



.



.

.

 

[Ken Snell]

You're welcome.

--
Ken Snell
<MS ACCESS MVP>

Success! Thank you very much!
Now it seems such an easy solution it should have been
obvious to me. Thanks again!
Erin

-----Original Message-----
Erin -

I found a post on another newsgroup that said the poster had contacted
Microsoft about this and had been told that there is a problem with the
Visible property of a form in a macro's SetValue action. I have not been
able to confirm this yet, but your info seems to match that of the other
poster's.

The workaround is to use VBA code to run that particular macro action. In
place of the SetValue action in your macro, put the RunCode action (we'll
set up a public function in a moment here) and tell the action that the
function argument is MakeFormInvisible() (included the () in the argument):
Action: RunCode
Function: MakeFormInvisible()

Then, go to the database window and click on Modules. Open a new module and
type the following into it:

Public Function MakeFormInvisible()
Forms!InputFormName.Form.Visible = False
End Function

(Replace InputFormName with the actual name of the form.)

Save the module and name it basFunctions.

This should now work for you. I'm still checking on this "bug" possibility.

--
Ken Snell
<MS ACCESS MVP>

No, it didn't work, but it did change my error message to
always display the one about not having the license
required to display that Active X control (instead of the
usual about visible not being a property of forms).

I checked my references in VBA again. The article I
referenced below says I need Microsoft Active X Data
Objects 2.1 Library Reference and 2.5 Library Reference. I
am only able to have one or the other or I get an error
stating that name conflicts with an existing library. The
macro won't run whichever reference I set.

I can't find any other information at their website that
looks like it would relate to this problem, either.


-----Original Message-----
I know of no reason why this wouldn't work for you.

Try using the full reference to the form's visible
property in the Item box:
Forms!InputFormName.Form.Visible

And use this in the Expression box:
False

See if that works.

message
Yes, thanks.

I created a db in Access 2000. There are several reports
which are each built upon several parameter queries. I
use
a form to ask for the parameter which then supplies the
parameter to all queries and prints the parameter in the
report. On opening the report the macro opens the user
input form, the OK button on the form hides the
form, keeping it open, so the queries can access the
parameter. Closing the report closes the form. This is
straight from Access Help files and is something my
users
use daily. It has always worked beautifully.

I upgraded to Access 2003 and now the macro errors at
the
SetValue action (Object: my input form, Property:
[Visible] Value: No)that hides the form. I get an error
message stating that "there is an invalid reference to
the
property visible. The property may not exist or may not
apply to the object specified." But Access'
documentation
says that the visible property does apply to a form.
Sometimes I get the message that I need to register my
Active X control, (I am only using the standard command
button on the form toolbox). So I tried making sure I
had
all my needed references set per online help article - I
don't have the article #, but it is titled "References
that you must set when you use Office Access 2003." I am
unable to set any references. I get error message then
that says the "name conflicts with an existing module,
project or library."

I have tried Office Updates and repairing my
installation
(as well as swearing and making faces at the monitor).

This should work! Is this a bug with 2003? I can't allow
my company to install the upgrades we already obtained
if
the databases won't work after!

Thanks very much for your help.

Erin


-----Original Message-----
I have not seen other similar problems with A2003, so
perhaps it is related
to your specific code/macro? Can you post more
information here about what
you were doing and what isn't working?

--
Ken Snell
<MS ACCESS MVP>

message
Yes, but this won't work if you have Access 2003! The
Set
Value action to hide the form while keeping it open
for
the queries to access won't work! There are 4
postings
about this problem in this group since Christmas,
but no
answers to the problem:

Macro problem macro frustration 1/2/04
Macro action failed 1/14/04
Problem with Macro 1/19/04
Macro errors after 2003 upgrad! 1/19/04 (mine)
(and another of mine from 12/22/03)

Can anyone help?



-----Original Message-----
Not directly.

If you want this option, then don't use the built-
in "parameter" box
(actually an InputBox). Create your own form that
allows
the user to enter
the desired value(s) into textbox(es) and then they
can
click an OK (or Run)
command button, or they can click a Cancel button.
You
then have each button
run its own code to either run the query (OK) or not
run
the query (Cancel).
You then change the query so that it uses the form's
textbox as its source
for the parameter:
[Forms]![FormName]![TextBoxName]


--
Ken Snell
<MS ACCESS MVP>

message
I have a form that is populated by way of a macro
that
runs, among other things, a parameter query. The
problem
is that, if a user presses cancel on one of the
parameters' dialog boxes, the macro halts and
reports as
much in a very user-unfriendly way. Users of the
database
panic and come running for advice!

Is there a way I can, like with the macro Set
Warnings
setting, turn this off and have the macro just
halt
quietly!?!

Thanks,
BJM


.



.



.

.