Cannot view results of query

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

All,

We have created a shared Access 2003 database and some users are not able to
view the results of a query we created. One user can sit at a specific PC,
login to the database and view the results, but when another user performs
the exact same task, the results are not shown.

The DB is password-protected, but that does not seem to be the issue. The
folder where the DB sits has the correct permissions. The network folks
claim it is a DB problem, but the security settings are the same within our
DB and the folder in which it sits.

Any ideas would be greatly appreciated! Please let me know if more
informaiton is needed to describe this problem.

Thank you!

Scott
 
Hi, Scott.
some users are not able to
view the results of a query we created. One user can sit at a specific PC,
login to the database and view the results, but when another user performs
the exact same task, the results are not shown.

This implies that the query runs, but only an hourglass is displayed. I
suspect instead that there is a specific error message when these users
attempt to run the query. What is the error message?

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.)
 
Gunny,

Thank you for your response.

Unfortunately there is neither an hourglass nor an error message....this is
why we're stumped.

The 'results' screen is returned, however the members of the group (results
of the 'group' query) are not present. The page's view is normal, however
the records queried are not present.

Any other suggestions?

Please advise, thank you.

Scott
 
Hi, Scott.

So your query returns records for some users, but zero records for others.
The good news is that the query works. (It's not working the way you
expect, though.)

You mention members of the "Group" are not returned by the query. Are the
users who see no results not members of the same group as the users who see
results? Or are these users members of a different group that the users who
see results are not a part of?

And have you named your query or a field "Group"? This is not recommended.
Group is a Reserved word. Using Reserved words in queries, VBA code or
macros can give errors and unexpected results.

I would begin the investigation by looking at the query's criteria. Look at
the WHERE clause and HAVING clause, and any Immediate IF (IIF), Chose( ) or
Switch( ) functions, as well as those of any subqueries involved. These may
cut the criteria down enough so that no records qualify for the resulting
record set for a given user.

Your description sounds like you have shared-level security (database
password only), not user-level security (UserID and password). But if
user-level security is applied, then that could also be cutting down the
criteria in the query, since the user could lack permissions necessary to
return certain records from the query. Off of the top of my head, I can't
think of any situations that _wouldn't_ return an error message though, such
as "No read permissions" on a query or table.

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.)
 
Gunny,

Yes, the query works; it is just the results that some users are having
trouble viewing. And yes, this is shared-level DB, not user-level.

Group is actually a table, and the query pulls results from the Group table
which is linked to the Master table. The results, however, do not show up
when a couple of particular users run the query.

The entire DB is in one folder and is actually just one file....this is
baffling us. Would you suggest changing the name of the table to something
other than Group?

Please advise, thank you, and thank you for your help!

Scott
 
Hi, Scott.
Would you suggest changing the name of the table to something
other than Group?

Yes. But be aware that a number of things in your application will probably
break. Every object that depends upon this table, such as queries and the
record sources of forms, will need to have the reference name changed to the
new name. If you have Access 2003, you can check object dependencies easily
before you make a change, so that you know which objects are going to be
affected.

Changing the name from Group to tblGroup would be a common naming convention
that's easily recognizable as the name of a table in the database. Make the
change when there's plenty of time to test everything to make sure the
application works properly, not five minutes before everybody who uses the
database is due back from a lunch break.
Please advise

I suggest that you post a new question in the
Microsoft.Public.Access.Queries newsgroup where lots of query whizzes hang
out. You'll get a quicker response there than if you post a problem query
in this newsgroup at this time of day. Post the SQL statement of the query
along with the relevant information, like no user-level security, no linked
tables, no error message, users run the same query on the same computer, but
some users see records while others get zero records returned from the
query, et cetera.

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.)
 
Back
Top