S
Scott
Okay-- I have scoured the internet and the messageboards
for a solution to this seemingly novice question. I haven't
found any documentation or messages that even remotely comes close
to solving this problem. Much appreciation if anyone out there can
help me find the answer.
Setup:
I have a form in an MS Access 2002 Database Project, using
SQL 2000 as the back end. The form has 5 fields with text boxes which
I have enabled to be searched through with the Filter By Form
function within Access. Now, I setup the database defaults through the
Tools --> Options --> Edit/Find. I setup the max list at 20000
rows, and on the form itself I set up each textbox's FilterLookup property
to Always.
The maximum amount of rows per text box is around 2000
each. So-- There _should_ be no chance there that I will get the ill
fated "Is Null" + "Is Not Null" problem.
It works fine under my development user account, as I have
full system privaledges setup with the Server Role "System
Administrators".
However, under any SQL 2000 user account, the user will
consistently run into the error of getting the "Is Null", "Is Not Null"
problem when trying to do a Filter By Form search. The ONLY
solution I have ran into is setting each user to be part of the Server
Role "System Administrators", thus bypassing any amount of security
that I want to enforce on the database level (BAD).
Now-- The only thing I can suppose is that Access is
fine, but somewhere on the SQL server level something is a bit
screwy with a permission setting somewhere. The database goes into
production tomorrow, and I will have to setup each user as a system
administrator for the time being so that any user can do a simple Filter
By Form search; this is what I feared the most-- to get full
functionality and data integrety I need to figure out a way to make this
work without comprimising the security of the entire system.
Thank you for any of your help and time,
Scott Landes
for a solution to this seemingly novice question. I haven't
found any documentation or messages that even remotely comes close
to solving this problem. Much appreciation if anyone out there can
help me find the answer.
Setup:
I have a form in an MS Access 2002 Database Project, using
SQL 2000 as the back end. The form has 5 fields with text boxes which
I have enabled to be searched through with the Filter By Form
function within Access. Now, I setup the database defaults through the
Tools --> Options --> Edit/Find. I setup the max list at 20000
rows, and on the form itself I set up each textbox's FilterLookup property
to Always.
The maximum amount of rows per text box is around 2000
each. So-- There _should_ be no chance there that I will get the ill
fated "Is Null" + "Is Not Null" problem.
It works fine under my development user account, as I have
full system privaledges setup with the Server Role "System
Administrators".
However, under any SQL 2000 user account, the user will
consistently run into the error of getting the "Is Null", "Is Not Null"
problem when trying to do a Filter By Form search. The ONLY
solution I have ran into is setting each user to be part of the Server
Role "System Administrators", thus bypassing any amount of security
that I want to enforce on the database level (BAD).
Now-- The only thing I can suppose is that Access is
fine, but somewhere on the SQL server level something is a bit
screwy with a permission setting somewhere. The database goes into
production tomorrow, and I will have to setup each user as a system
administrator for the time being so that any user can do a simple Filter
By Form search; this is what I feared the most-- to get full
functionality and data integrety I need to figure out a way to make this
work without comprimising the security of the entire system.
Thank you for any of your help and time,
Scott Landes