i have an access 2003 adp project with a sql server 2000 backend. i have a form that is opened with the standard docmd.openform and includes a filter for foreign key value, which sets the form's "serverfilter" property to something like "testPassExecutionID=65", for example.
the form displays records to test case executions (i'm in QA for a software company) and includes a combobox for status, which can have a value of "Pending", "Pass", "Fail". i also have another combobox which is used to filter the display of records based on a given status. if the user sets this to "Pending", for example, then the "serverfilter" property is modified to look something like "testPassExecutionID=65 and status='Pending'" and i call the refresh command. all of this works fine.
my problem is, once this filter is applied, if the user then changes the status for a given record, i get an access message popup that states...
is there a way that i can suppress this message? i have reason to believe it is causing some other problems in areas of my code where the code is attempting to navigate away from a record that triggers this. i tried using "docmd.setwarning false" and that didn't work.
the form displays records to test case executions (i'm in QA for a software company) and includes a combobox for status, which can have a value of "Pending", "Pass", "Fail". i also have another combobox which is used to filter the display of records based on a given status. if the user sets this to "Pending", for example, then the "serverfilter" property is modified to look something like "testPassExecutionID=65 and status='Pending'" and i call the refresh command. all of this works fine.
my problem is, once this filter is applied, if the user then changes the status for a given record, i get an access message popup that states...
The data was added to the database but the data won't be displayed in the form because it doesn't satisfy the criteria in the underlying record source.
is there a way that i can suppress this message? i have reason to believe it is causing some other problems in areas of my code where the code is attempting to navigate away from a record that triggers this. i tried using "docmd.setwarning false" and that didn't work.