Using a time frame, now asks for it even for design view

P

Paul (ESI)

I am using a time frame criteria in several queries. Those queries are then
used for other queries, so all queries connected ask for the time frame. The
problem I am running into is that now I am being asked to enter a time frame
almost no matter what I do with the queries that do not directly have the
time frame criteria. For example, if I try to get in design view, it asks for
a time frame. Why would it need a time frame?! I'm just trying to look at the
design view. Also, when I actually run one of the queries (other than those
that have the date frame criteria in them) it will often ask for the time
frame twice. Anybody know what may be causing my problems?

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy

~~~~~~
| |
|c--OD
| _)
| |
|-. |
/ `-# /A
/ /_|..`#.J/
||LJ `m''
ptaylor
 
6

'69 Camaro

Hi, Paul.
Anybody know what may be causing my problems?
Click to expand...

Once upon a time, you sorted or filtered on this time frame field in
Datasheet View, then later changed the name of the field or changed the data
source that produced this field (such as using the same field in a different
joined table). Then you made copies of this query, changed the SQL
appropriately and named the new queries, thereby propogating these properties
to the other queries.

Or you placed this field in the base query, then later changed its data
source.

Or you have a parameter query that uses time frame as a parameter and don't
realize it.

First, open the Design View of each of these queries and select the upper
pane (with the tables) and right-click and select "Properties" on the pop-up
menu. Check the "Filter" and "Order By" Properties to ensure that the time
frame isn't listed. If it is then remove it.

If it's not there, then check the SQL View pane of each of these queries and
see if any of them start with the word PARAMETERS. If so, that's where the
mystery flows from. You probably want to keep this parameter, but you'll
have to decide.

If it's not there, then you'll have to search each of the queries for the
fields displayed, sorted on, and within expressions to find the time frame
field that doesn't belong. The ones that don't belong are the ones that
don't exist in the data sources, usually due to misspellings or removal of
these fields from the original table data source in the query, or removal of
the original table data source where this field came from.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)

- - -
When you see correct answers to your question posted in Microsoft's Online
Community, please sign in to the Community and mark these posts as "Answers,"
so that all may benefit by filtering on "Answered questions" and quickly
finding the right answers to similar questions. Remember that questions
answered the quickest are often from those who have a history of rewarding
the contributors who have taken the time to answer questions correctly.
 
P

Paul (ESI)

Done, done, and done. Nothing you mention is causing the problem in my case.
I never sorted or filtered using the time frame (unless, by filtering, you
actually mean the usage of the criteria in the first place to pull over only
those dates for the query. Also, the name of the field has remained the same
the entire time I've used it. I also did not copy the query. I just made new
queries for the next level queries.

I also tried all of your suggestions to follow about parameter queries, and
none were the case for me. The dates are only defined as a parameter in the
cross-tab query. Before I did this, the third level query (pulls from the
crosstab query, which pulls from a query before it) would not work. It worked
fine once I put the parameters in the crosstab query, but I ran into these
problems. Thanks for your help. So far, though, I'm still getting the
problem. It is not a big deal anyway, though. At least everything runs
properly. It's just weird.

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy

~~~~~~
| |
|c--OD
| _)
| |
|-. |
/ `-# /A
/ /_|..`#.J/
||LJ `m''
ptaylor
 
6

'69 Camaro

Hi, Paul.
So far, though, I'm still getting the
problem.
Click to expand...

Jet may be "helping" you. Jet rewrites the SQL code any time the query is
opened in Design View. You may want to go over the SQL with a fine toothed
comb, especially if you use multiple joins, or subqueries, or table and field
names with non-alphanumeric characters (an underline is the exception). If
you used a field named "time frame" instead of "TimeFrame" or "Time_Frame,"
and expect that putting brackets around it "will work every time! It's true
because I read it on the Internet!" you'll find occasional mysteries like
this one that take a long time to dig out the truth.

Other than that, possibly recreating the queries from scratch will fix the
problem, but I'd focus first on the base queries that the other queries use
as a data source.

I don't have any more ideas, so perhaps someone else does. (Well, you could
create a new database file and import all the objects from this one into it,
but that probably won't help.)

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)

- - -
When you see correct answers to your question posted in Microsoft's Online
Community, please sign in to the Community and mark these posts as "Answers,"
so that all may benefit by filtering on "Answered questions" and quickly
finding the right answers to similar questions. Remember that questions
answered the quickest are often from those who have a history of rewarding
the contributors who have taken the time to answer questions correctly.
 
Top