Run macro if query is not null

[tina]

Karen, i've gotten really curious as to why this won't work for you, despite
the best efforts of everyone involved. if your db is A97 or newer, and if
you want me to look at a copy of it (with any proprietary info removed), to
see if i can figure out what's going on, then post back with an email
address and i'll send you an email. make sure to disguise your email address
(so you don't get spammed), and tell me how to "un-disguise" it so it will
work.

I am completely lost now. I did study what you suggest and laid out for the
last couple of hours and I couldn't get it. Perhaps like you said, there is
something wrong in my DB, I am confused now, I guess I have to stop now, it's
almost 12 midnight. I will try to figure out tomorrow with a fresh mind...
till later, thanks again
Karen

Let's confirm that you've put the DCount expression in the column named
"Condition" in the macro's design view? If you have done that, and you still
get the "parsing" error for the DCount function, then there is something
wrong with your database file. I've never seen this error before, so I could
only guess as to its cause -- but it might be the references in the
database. Confirm (as tina asked before) that you have the expression in the
correct place.

As for using a textbox on a form as the source of a parameter's value, where
you had a parameter such as [Enter your ID:] in the query, replace it with a
reference to the form's textbox:
[Forms]![NameOfYourForm]![NameOfYourTextbox]

The form must be open when the query runs.
--

Ken Snell
<MS ACCESS MVP>

Thanks, Ken.
I am sorry, I don't understand exactly how to work on the form you
suggested. Would you mind detail the procedures for me?

Let me explain what I was doing : I have a form for employees to fill out
his own week time-records and there is a CmdBut on this "form". After
filling out his own records, he has to submit his records. All those
submitted records were in a table which consists of all the IDs' records,
if
the user is not sure about the records been submitted, he then click this
CmdBut by keying in his own ID and the weekno. to view his own records for
the week. These records are pulled out by this query through those
parameters. That's why I want to add a MsgBox to add to the Macro for
that
CmdBut and if there is no record shown on the query, the MsgBox will tell
the
user to proceed. If the query data-sheet shows the record, no
MsgBox....etc

Because of what your saying about the DCount not working in a parameter
query, I've just created a form by using the same query.
Same thing, DCount doesn't let me go through the macro setup, i.e. I can't
even save the macro with DCount...
So I put the condition for the Macro with MsgBox as follows:

[Forms]![05frmChkWkEntry]![TT] Is Null

the parameters did come up for ID and Week, then the form comes up with or
without records for the input-week, but no msgbox comes up despite records
shown or not.

So If msgbox does not work with parameter criteria, I think I'd better
drop
the idea what I want and I'll let msg box pop up in any case and I'll just
change the Text in the msgbox. (It took too much valuable time of you
guys,
sorry.)

Ken, while I just finished the above form, I've discovered another problem
of the sequence of the field. I want to sort the form to display by date,
so
I put in the property of that form with ON ORDER : [Date] ASC
but it didn't work.

Again, I would appreciate for all the help you guys offered.

thanks
karen

:

I don't believe that the DCount function will do what you want with a
parameter query, as it won't ask you for the parameters' values in order
to
run itself. I just tested a simple setup in a database here, and the
DCount
condition did not cause the macro to post a message box for me (and it
didn't ask me for the parameters)...it also didn't throw an error at me.

You'll need to use a form for the user to put the ID number and the week
number into textboxes, and then let the query read the values from the
form
instead of asking for the parameters. That way, the DCount function
should
work just fine for you.

--

Ken Snell
<MS ACCESS MVP>



Myy query is an ordinary query (select) but with 2 criteria (I put down
my
real criteria) [Enter your ID No:] with field "employeeID" and [Enter
WeekNo:] with field "Week". I want to do: when there is no record for
that
employee in that week, no message pops up and if there is/are record,
the
message will pop up to ask him to proceed the action further...
I am sorry to take up so much of your time, I was hoping it wouldn't be
that
difficult.
thanks
karen

:

is your query an "ordinary" query, that returns a set of records? or
is
it
an Action query, such as Update, Delete, Append, Make-Table?


btw, in order not to give confusion, I did mention in one of my
previous
messages using prefixed Usys for my qry, I changed that already
because
I
thought that was the cause, so my qry now is without Usys-prefix.
thanks,
Karen

:

DCount("*","Qry05userChkWkEntry") = 0
and I also tried
DCount("[TT]","Qry05userChkWkEntry") = 0

Both didn't let me go through, same error msg.
Karen

:

DCount("*", "MyQueryName") = 0


--

Ken Snell
<MS ACCESS MVP>

"Karen Yeung/Holland"
<[email protected]>
wrote in
message
Tina, I I hope you are still there and able to read my problem
related to
what you wrote on the subject.
I am Karen and have read this subject and think this is
similar
as
what I
am
trying to do. So I tried what you wrote but I got an error
message :
Miscrosoft Access can't parse the expression: 'DCount(1,
"MyQueryName") >
0'
I also tried DCount(1, "MyQueryName")=0
My sequence of macros:
OpenQuery
MsgBox (with the above condition)
... Cancel Event
StopMacro
I used the expression for MsgBox's condition. My query is
prefixed
as
uSys... and with [paremeter criteria], I hope this is not the
problem.

I want: if the query result is zero row, the MsgBox pops up.
Now
the
problem is that it doesn't even accept my condition ?
Help please, anybody?
thanks
Karen

:

Can you help me write the condition which means, if query
result
is
empty.

it would be easier to have the condition dictate when to send
the
email,
rather than when to not send it. try adding a condition to
the
macro
action
that begins the "send email" process, as

DCount(1,"MyQueryName") > 0

if the number of records in the query is zero, then the
action
doesn't
run.
if your "send email" process is several consecutive macro
actions,
make
sure
that the subsequent actions have an ellipsis (...) in the
condition
column.

hth


Thank you for your reply.

Can you help me write the condition which means, if query
result
is
empty.
Best regards
--
Bassel


:

In macro design view click on the menu VIEW - Conditions.
Add the condition.

:

Hello
I am using a macro that runs on daily basis to send an
email
of a
certain
query results.

The query results are sometimes empty.
Is it possible to cancel sending the mail , if the
query
result is
null.

Thank you and beat regards

 

[Guest]

Sorry for the late reply due to our time difference and I have to work today.
I would love to send this over to you, tina. I am afraid I don't understand
what u mean by "disguise"my email address or "un-disguise". Pls let me know
to send it to you. thanks, Karen

Karen, i've gotten really curious as to why this won't work for you, despite
the best efforts of everyone involved. if your db is A97 or newer, and if
you want me to look at a copy of it (with any proprietary info removed), to
see if i can figure out what's going on, then post back with an email
address and i'll send you an email. make sure to disguise your email address
(so you don't get spammed), and tell me how to "un-disguise" it so it will
work.

I am completely lost now. I did study what you suggest and laid out for the
last couple of hours and I couldn't get it. Perhaps like you said, there is
something wrong in my DB, I am confused now, I guess I have to stop now, it's
almost 12 midnight. I will try to figure out tomorrow with a fresh mind...
till later, thanks again
Karen

Let's confirm that you've put the DCount expression in the column named
"Condition" in the macro's design view? If you have done that, and you still
get the "parsing" error for the DCount function, then there is something
wrong with your database file. I've never seen this error before, so I could
only guess as to its cause -- but it might be the references in the
database. Confirm (as tina asked before) that you have the expression in the
correct place.

As for using a textbox on a form as the source of a parameter's value, where
you had a parameter such as [Enter your ID:] in the query, replace it with a
reference to the form's textbox:
[Forms]![NameOfYourForm]![NameOfYourTextbox]

The form must be open when the query runs.
--

Ken Snell
<MS ACCESS MVP>



Thanks, Ken.
I am sorry, I don't understand exactly how to work on the form you
suggested. Would you mind detail the procedures for me?

Let me explain what I was doing : I have a form for employees to fill out
his own week time-records and there is a CmdBut on this "form". After
filling out his own records, he has to submit his records. All those
submitted records were in a table which consists of all the IDs' records,
if
the user is not sure about the records been submitted, he then click this
CmdBut by keying in his own ID and the weekno. to view his own records for
the week. These records are pulled out by this query through those
parameters. That's why I want to add a MsgBox to add to the Macro for
that
CmdBut and if there is no record shown on the query, the MsgBox will tell
the
user to proceed. If the query data-sheet shows the record, no
MsgBox....etc

Because of what your saying about the DCount not working in a parameter
query, I've just created a form by using the same query.
Same thing, DCount doesn't let me go through the macro setup, i.e. I can't
even save the macro with DCount...
So I put the condition for the Macro with MsgBox as follows:

[Forms]![05frmChkWkEntry]![TT] Is Null

the parameters did come up for ID and Week, then the form comes up with or
without records for the input-week, but no msgbox comes up despite records
shown or not.

So If msgbox does not work with parameter criteria, I think I'd better
drop
the idea what I want and I'll let msg box pop up in any case and I'll just
change the Text in the msgbox. (It took too much valuable time of you
guys,
sorry.)

Ken, while I just finished the above form, I've discovered another problem
of the sequence of the field. I want to sort the form to display by date,
so
I put in the property of that form with ON ORDER : [Date] ASC
but it didn't work.

Again, I would appreciate for all the help you guys offered.

thanks
karen

:

I don't believe that the DCount function will do what you want with a
parameter query, as it won't ask you for the parameters' values in order
to
run itself. I just tested a simple setup in a database here, and the
DCount
condition did not cause the macro to post a message box for me (and it
didn't ask me for the parameters)...it also didn't throw an error at me.

You'll need to use a form for the user to put the ID number and the week
number into textboxes, and then let the query read the values from the
form
instead of asking for the parameters. That way, the DCount function
should
work just fine for you.

--

Ken Snell
<MS ACCESS MVP>



Myy query is an ordinary query (select) but with 2 criteria (I put down
my
real criteria) [Enter your ID No:] with field "employeeID" and [Enter
WeekNo:] with field "Week". I want to do: when there is no record for
that
employee in that week, no message pops up and if there is/are record,
the
message will pop up to ask him to proceed the action further...
I am sorry to take up so much of your time, I was hoping it wouldn't be
that
difficult.
thanks
karen

:

is your query an "ordinary" query, that returns a set of records? or
is
it
an Action query, such as Update, Delete, Append, Make-Table?


btw, in order not to give confusion, I did mention in one of my
previous
messages using prefixed Usys for my qry, I changed that already
because
I
thought that was the cause, so my qry now is without Usys-prefix.
thanks,
Karen

:

DCount("*","Qry05userChkWkEntry") = 0
and I also tried
DCount("[TT]","Qry05userChkWkEntry") = 0

Both didn't let me go through, same error msg.
Karen

:

DCount("*", "MyQueryName") = 0


--

Ken Snell
<MS ACCESS MVP>

"Karen Yeung/Holland"
<[email protected]>
wrote in
message
Tina, I I hope you are still there and able to read my problem
related to
what you wrote on the subject.
I am Karen and have read this subject and think this is
similar
as
what I
am
trying to do. So I tried what you wrote but I got an error
message :
Miscrosoft Access can't parse the expression: 'DCount(1,
"MyQueryName") >
0'
I also tried DCount(1, "MyQueryName")=0
My sequence of macros:
OpenQuery
MsgBox (with the above condition)
... Cancel Event
StopMacro
I used the expression for MsgBox's condition. My query is
prefixed
as
uSys... and with [paremeter criteria], I hope this is not the
problem.

I want: if the query result is zero row, the MsgBox pops up.
Now
the
problem is that it doesn't even accept my condition ?
Help please, anybody?
thanks
Karen

:

Can you help me write the condition which means, if query
result
is
empty.

it would be easier to have the condition dictate when to send
the
email,
rather than when to not send it. try adding a condition to
the
macro
action
that begins the "send email" process, as

DCount(1,"MyQueryName") > 0

if the number of records in the query is zero, then the
action
doesn't
run.
if your "send email" process is several consecutive macro
actions,
make
sure
that the subsequent actions have an ellipsis (...) in the
condition
column.

hth


Thank you for your reply.

Can you help me write the condition which means, if query
result
is
empty.
Best regards
--
Bassel


:

In macro design view click on the menu VIEW -

 

[tina]

well, i rarely post my email address, even disguised. quite frankly, i
figure it's up to the person asking for help to decide if they want to take
the risk of posting their own email address. then i email the person, and
s/he emails the db back to me. if you decide you want to post your email
address, the best you can do is to disguise the address to make it harder
(hopefully impossible) for data miners to pick it out of the message text.
for example, the fake email address my newsreader uses is
(e-mail address removed)
now, if that were a "real" email address, i might try to disguise it by
typing it as nostphiamsatiadsdrfesasdoktceom and tell you to remove the
letters "this is fake" in order, from left to right, and then convert the
letters at to @ and dot to . to get the correct address.

hth

Sorry for the late reply due to our time difference and I have to work today.
I would love to send this over to you, tina. I am afraid I don't understand
what u mean by "disguise"my email address or "un-disguise". Pls let me know
to send it to you. thanks, Karen

Karen, i've gotten really curious as to why this won't work for you, despite
the best efforts of everyone involved. if your db is A97 or newer, and if
you want me to look at a copy of it (with any proprietary info removed), to
see if i can figure out what's going on, then post back with an email
address and i'll send you an email. make sure to disguise your email address
(so you don't get spammed), and tell me how to "un-disguise" it so it will
work.

I am completely lost now. I did study what you suggest and laid out

for
the

last couple of hours and I couldn't get it. Perhaps like you said,

there
is

something wrong in my DB, I am confused now, I guess I have to stop

now,
it's

almost 12 midnight. I will try to figure out tomorrow with a fresh mind...
till later, thanks again
Karen

:

Let's confirm that you've put the DCount expression in the column named
"Condition" in the macro's design view? If you have done that, and

you
still

get the "parsing" error for the DCount function, then there is something
wrong with your database file. I've never seen this error before, so

I
could

only guess as to its cause -- but it might be the references in the
database. Confirm (as tina asked before) that you have the

expression in
the

correct place.

As for using a textbox on a form as the source of a parameter's

value,
where

you had a parameter such as [Enter your ID:] in the query, replace

it
with a

reference to the form's textbox:
[Forms]![NameOfYourForm]![NameOfYourTextbox]

The form must be open when the query runs.
--

Ken Snell
<MS ACCESS MVP>



Thanks, Ken.
I am sorry, I don't understand exactly how to work on the form you
suggested. Would you mind detail the procedures for me?

Let me explain what I was doing : I have a form for employees to

fill
out

his own week time-records and there is a CmdBut on this "form". After
filling out his own records, he has to submit his records. All those
submitted records were in a table which consists of all the IDs' records,
if
the user is not sure about the records been submitted, he then

click
this

CmdBut by keying in his own ID and the weekno. to view his own

records
for

the week. These records are pulled out by this query through those
parameters. That's why I want to add a MsgBox to add to the

Macro
for

that
CmdBut and if there is no record shown on the query, the MsgBox

will
tell

the
user to proceed. If the query data-sheet shows the record, no
MsgBox....etc

Because of what your saying about the DCount not working in a parameter
query, I've just created a form by using the same query.
Same thing, DCount doesn't let me go through the macro setup, i.e.

I
can't

even save the macro with DCount...
So I put the condition for the Macro with MsgBox as follows:

[Forms]![05frmChkWkEntry]![TT] Is Null

the parameters did come up for ID and Week, then the form comes up with or
without records for the input-week, but no msgbox comes up despite records
shown or not.

So If msgbox does not work with parameter criteria, I think I'd better
drop
the idea what I want and I'll let msg box pop up in any case and

I'll
just

change the Text in the msgbox. (It took too much valuable time of you
guys,
sorry.)

Ken, while I just finished the above form, I've discovered another problem
of the sequence of the field. I want to sort the form to display

by
date,

so
I put in the property of that form with ON ORDER : [Date] ASC
but it didn't work.

Again, I would appreciate for all the help you guys offered.

thanks
karen

:

I don't believe that the DCount function will do what you want with a
parameter query, as it won't ask you for the parameters' values

in
order

to
run itself. I just tested a simple setup in a database here, and the
DCount
condition did not cause the macro to post a message box for me

(and
it

didn't ask me for the parameters)...it also didn't throw an error

at
me.

You'll need to use a form for the user to put the ID number and

the
week

number into textboxes, and then let the query read the values

from
the

form
instead of asking for the parameters. That way, the DCount function
should
work just fine for you.

--

Ken Snell
<MS ACCESS MVP>



Myy query is an ordinary query (select) but with 2 criteria (I

put
down

my
real criteria) [Enter your ID No:] with field "employeeID" and [Enter
WeekNo:] with field "Week". I want to do: when there is no

record
for

that
employee in that week, no message pops up and if there is/are record,
the
message will pop up to ask him to proceed the action further...
I am sorry to take up so much of your time, I was hoping it wouldn't be
that
difficult.
thanks
karen

:

is your query an "ordinary" query, that returns a set of

records?
or

is
it
an Action query, such as Update, Delete, Append, Make-Table?


btw, in order not to give confusion, I did mention in one of my
previous
messages using prefixed Usys for my qry, I changed that already
because
I
thought that was the cause, so my qry now is without Usys-prefix.
thanks,
Karen

:

DCount("*","Qry05userChkWkEntry") = 0
and I also tried
DCount("[TT]","Qry05userChkWkEntry") = 0

Both didn't let me go through, same error msg.
Karen

:

DCount("*", "MyQueryName") = 0


--

Ken Snell
<MS ACCESS MVP>

"Karen Yeung/Holland"
<[email protected]>
wrote in
message
Tina, I I hope you are still there and able to read my problem
related to
what you wrote on the subject.
I am Karen and have read this subject and think this is
similar
as
what I
am
trying to do. So I tried what you wrote but I got an error
message :
Miscrosoft Access can't parse the expression: 'DCount(1,
"MyQueryName") >
0'
I also tried DCount(1, "MyQueryName")=0
My sequence of macros:
OpenQuery
MsgBox (with the above condition)
... Cancel Event
StopMacro
I used the expression for MsgBox's condition. My query is
prefixed
as
uSys... and with [paremeter criteria], I hope this is

not
the

problem.

I want: if the query result is zero row, the MsgBox

pops
up.

Now
the
problem is that it doesn't even accept my condition ?
Help please, anybody?
thanks
Karen

:

Can you help me write the condition which means, if query
result
is
empty.

it would be easier to have the condition dictate when

to
send

the
email,
rather than when to not send it. try adding a

condition
to

the
macro
action
that begins the "send email" process, as

DCount(1,"MyQueryName") > 0

if the number of records in the query is zero, then the
action
doesn't
run.
if your "send email" process is several consecutive macro
actions,
make
sure
that the subsequent actions have an ellipsis (...) in the
condition
column.

hth



Thank you for your reply.

Can you help me write the condition which means, if query
result
is
empty.
Best regards
--
Bassel


:

In macro design view click on the menu VIEW -

 

[Guest]

Tina,
Thank you so much for the explanation for that, again I've learned
something. I think I am not going to post it as from what you said in order
to play safe.
I am not an IT-person but a user of MS-Access only. I want to take this
opportunity to appreciate for all the help from all of you who helped me out
in completing this DB. Besides the replies from the questions I posted, the
answers to the other posts were also a helping tool to me. I have told my
Boss and the others this "Discusson Group" is a very good source for
learning.
I have to close this subject now, this is not a big problem even though I
let MsgBox pop out, because I have a dead line to go. sorry.
Can I post other questions in the future if I have other problems? I am a
sincere learner.

thanks and best regards to all
Karen

well, i rarely post my email address, even disguised. quite frankly, i
figure it's up to the person asking for help to decide if they want to take
the risk of posting their own email address. then i email the person, and
s/he emails the db back to me. if you decide you want to post your email
address, the best you can do is to disguise the address to make it harder
(hopefully impossible) for data miners to pick it out of the message text.
for example, the fake email address my newsreader uses is
(e-mail address removed)
now, if that were a "real" email address, i might try to disguise it by
typing it as nostphiamsatiadsdrfesasdoktceom and tell you to remove the
letters "this is fake" in order, from left to right, and then convert the
letters at to @ and dot to . to get the correct address.

hth

Sorry for the late reply due to our time difference and I have to work today.
I would love to send this over to you, tina. I am afraid I don't understand
what u mean by "disguise"my email address or "un-disguise". Pls let me know
to send it to you. thanks, Karen

Karen, i've gotten really curious as to why this won't work for you, despite
the best efforts of everyone involved. if your db is A97 or newer, and if
you want me to look at a copy of it (with any proprietary info removed), to
see if i can figure out what's going on, then post back with an email
address and i'll send you an email. make sure to disguise your email address
(so you don't get spammed), and tell me how to "un-disguise" it so it will
work.


I am completely lost now. I did study what you suggest and laid out for
the
last couple of hours and I couldn't get it. Perhaps like you said, there
is
something wrong in my DB, I am confused now, I guess I have to stop now,
it's
almost 12 midnight. I will try to figure out tomorrow with a fresh
mind...
till later, thanks again
Karen

:

Let's confirm that you've put the DCount expression in the column named
"Condition" in the macro's design view? If you have done that, and you
still
get the "parsing" error for the DCount function, then there is something
wrong with your database file. I've never seen this error before, so I
could
only guess as to its cause -- but it might be the references in the
database. Confirm (as tina asked before) that you have the expression in
the
correct place.

As for using a textbox on a form as the source of a parameter's value,
where
you had a parameter such as [Enter your ID:] in the query, replace it
with a
reference to the form's textbox:
[Forms]![NameOfYourForm]![NameOfYourTextbox]

The form must be open when the query runs.
--

Ken Snell
<MS ACCESS MVP>



Thanks, Ken.
I am sorry, I don't understand exactly how to work on the form you
suggested. Would you mind detail the procedures for me?

Let me explain what I was doing : I have a form for employees to fill
out
his own week time-records and there is a CmdBut on this "form". After
filling out his own records, he has to submit his records. All those
submitted records were in a table which consists of all the IDs'
records,
if
the user is not sure about the records been submitted, he then click
this
CmdBut by keying in his own ID and the weekno. to view his own records
for
the week. These records are pulled out by this query through those
parameters. That's why I want to add a MsgBox to add to the Macro
for
that
CmdBut and if there is no record shown on the query, the MsgBox will
tell
the
user to proceed. If the query data-sheet shows the record, no
MsgBox....etc

Because of what your saying about the DCount not working in a
parameter
query, I've just created a form by using the same query.
Same thing, DCount doesn't let me go through the macro setup, i.e. I
can't
even save the macro with DCount...
So I put the condition for the Macro with MsgBox as follows:

[Forms]![05frmChkWkEntry]![TT] Is Null

the parameters did come up for ID and Week, then the form comes up
with or
without records for the input-week, but no msgbox comes up despite
records
shown or not.

So If msgbox does not work with parameter criteria, I think I'd better
drop
the idea what I want and I'll let msg box pop up in any case and I'll
just
change the Text in the msgbox. (It took too much valuable time of you
guys,
sorry.)

Ken, while I just finished the above form, I've discovered another
problem
of the sequence of the field. I want to sort the form to display by
date,
so
I put in the property of that form with ON ORDER : [Date] ASC
but it didn't work.

Again, I would appreciate for all the help you guys offered.

thanks
karen

:

I don't believe that the DCount function will do what you want with a
parameter query, as it won't ask you for the parameters' values in
order
to
run itself. I just tested a simple setup in a database here, and the
DCount
condition did not cause the macro to post a message box for me (and
it
didn't ask me for the parameters)...it also didn't throw an error at
me.

You'll need to use a form for the user to put the ID number and the
week
number into textboxes, and then let the query read the values from
the
form
instead of asking for the parameters. That way, the DCount function
should
work just fine for you.

--

Ken Snell
<MS ACCESS MVP>



Myy query is an ordinary query (select) but with 2 criteria (I put
down
my
real criteria) [Enter your ID No:] with field "employeeID" and
[Enter
WeekNo:] with field "Week". I want to do: when there is no record
for
that
employee in that week, no message pops up and if there is/are
record,
the
message will pop up to ask him to proceed the action further...
I am sorry to take up so much of your time, I was hoping it
wouldn't be
that
difficult.
thanks
karen

:

is your query an "ordinary" query, that returns a set of records?
or
is
it
an Action query, such as Update, Delete, Append, Make-Table?


btw, in order not to give confusion, I did mention in one of my
previous
messages using prefixed Usys for my qry, I changed that already
because
I
thought that was the cause, so my qry now is without
Usys-prefix.
thanks,
Karen

:

DCount("*","Qry05userChkWkEntry") = 0
and I also tried
DCount("[TT]","Qry05userChkWkEntry") = 0

Both didn't let me go through, same error msg.
Karen

:

DCount("*", "MyQueryName") = 0


--

Ken Snell
<MS ACCESS MVP>

"Karen Yeung/Holland"
<[email protected]>
wrote in
message
Tina, I I hope you are still there and able to read my
problem
related to
what you wrote on the subject.
I am Karen and have read this subject and think this is
similar
as
what I
am
trying to do. So I tried what you wrote but I got an error
message :
Miscrosoft Access can't parse the expression: 'DCount(1,
"MyQueryName") >
0'
I also tried DCount(1, "MyQueryName")=0
My sequence of macros:
OpenQuery
MsgBox (with the above condition)

 

[tina]

Can I post other questions in the future if I have other problems? I am a

sincere learner.

of course you can, come back to the newsgroups anytime you have a specific
question or problem. there are always folks here who'll do their best to
help you out. sorry we weren't able to solve this one with you - that does
happen sometimes. good luck!