Error 3071

[Jennie]

OK, I admit I am an Access rookie, but can someone please tell me why I keep
getting this:

Error 3071
This expression is typed incorrectly, or it is too complex to be evaluated.
For example, a numeric expression may contain too many complicated elements.
Try simplifying the expression by assigning parts of the expression to
variables. (Error 3071)

Because of this:

strDocName = "Cites Query1"
DoCmd.OpenReport strDocName, acViewPreview

 

[Douglas J. Steele]

It's because of the space in the report name.

Try:

strDocName = "[Cites Query1]"

(or, better yet, don't use spaces in your names)

 

[Jennie]

Thanks!

It's because of the space in the report name.

Try:

strDocName = "[Cites Query1]"

(or, better yet, don't use spaces in your names)

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

OK, I admit I am an Access rookie, but can someone please tell me why I
keep
getting this:

Error 3071
This expression is typed incorrectly, or it is too complex to be
evaluated.
For example, a numeric expression may contain too many complicated
elements.
Try simplifying the expression by assigning parts of the expression to
variables. (Error 3071)

Because of this:

strDocName = "Cites Query1"
DoCmd.OpenReport strDocName, acViewPreview

 

[Angela]

Hi,
I have the same error coming up and I don't have a space in my report name.
This error is coming up when I am trying to link a sub report to a main
report. Any other suggestions?

Thanks,
Angela

It's because of the space in the report name.

Try:

strDocName = "[Cites Query1]"

(or, better yet, don't use spaces in your names)

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

OK, I admit I am an Access rookie, but can someone please tell me why I
keep
getting this:

Error 3071
This expression is typed incorrectly, or it is too complex to be
evaluated.
For example, a numeric expression may contain too many complicated
elements.
Try simplifying the expression by assigning parts of the expression to
variables. (Error 3071)

Because of this:

strDocName = "Cites Query1"
DoCmd.OpenReport strDocName, acViewPreview

 

[Douglas J. Steele]

Does the report open when you click on it through the GUI?


--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

Hi,
I have the same error coming up and I don't have a space in my report
name.
This error is coming up when I am trying to link a sub report to a main
report. Any other suggestions?

Thanks,
Angela

It's because of the space in the report name.

Try:

strDocName = "[Cites Query1]"

(or, better yet, don't use spaces in your names)

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

OK, I admit I am an Access rookie, but can someone please tell me why I
keep
getting this:

Error 3071
This expression is typed incorrectly, or it is too complex to be
evaluated.
For example, a numeric expression may contain too many complicated
elements.
Try simplifying the expression by assigning parts of the expression to
variables. (Error 3071)

Because of this:

strDocName = "Cites Query1"
DoCmd.OpenReport strDocName, acViewPreview

 

[Angela]

The main part of the report opens, the linked report does not open. Each
query that the reports are based on run fine individually.

I have linked the Employee number and the Pay period number in the link
master and link child fields. If I link the employee number on its own the
sub report runs fine, however, it is not specific enough.

Does the report open when you click on it through the GUI?


--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

Hi,
I have the same error coming up and I don't have a space in my report
name.
This error is coming up when I am trying to link a sub report to a main
report. Any other suggestions?

Thanks,
Angela

It's because of the space in the report name.

Try:

strDocName = "[Cites Query1]"

(or, better yet, don't use spaces in your names)

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



OK, I admit I am an Access rookie, but can someone please tell me why I
keep
getting this:

Error 3071
This expression is typed incorrectly, or it is too complex to be
evaluated.
For example, a numeric expression may contain too many complicated
elements.
Try simplifying the expression by assigning parts of the expression to
variables. (Error 3071)

Because of this:

strDocName = "Cites Query1"
DoCmd.OpenReport strDocName, acViewPreview

 

[Douglas J. Steele]

Sorry, you're not giving nearly enough details if you want help.

What are the tables involved? What's appearing on each report? Exactly what
have you put in the Master and Child link fields?

 

[Angela]

Hi Douglas,

Both reports are based on queries using the same tables. One of the queries
for the main report has a parameter for the employee number field, and a
greater than or equal to a beginning date and less than or equal to the
ending date field.

The sub report is based on the same tables as used in the main report,
however, it does not contain any parameters.

I have grouped the main report by the Beginning date and by the ending date.
The sub report is placed in the from date footer (although I have tried using
other footers for the sub report and it did not work there either).

in the link master and link child fields I have keyed in:

eeEENum;PPN
eeEENum;PPN

Both reports contain these fields

I don't know what else to say, they both seem like fairly simple reports /
queries, all the linked fields are formatted the same way etc. There isn't
really any complicated formulas etc. so there must just be something simple
that I am missing.

Any suggestions would help.

Thanks,
Angela

 

[Douglas J. Steele]

Sorry, I'm kind of distracted at the moment (my wife's having surgery), so
I'm finding I can't concentrate on your report. If no one else picks up this
thread, you might try reposting to microsoft.public.access.reports, giving
the details you've given below.

 

[Angela]

No problem. Thanks I will try that.

Sorry, I'm kind of distracted at the moment (my wife's having surgery), so
I'm finding I can't concentrate on your report. If no one else picks up this
thread, you might try reposting to microsoft.public.access.reports, giving
the details you've given below.