G
Guest
first off, i'm using A2K....
i want to create an update query that will let my users modify records in a
table because when they have to scroll through their usual data entry form it
takes too long to get to the record they need modify and i think a query
would run a little quicker -- that's my assumption.
if you grant my assumption, then what i see as the way to implement it
(since they don't know how to use the Access QBE interface, is by developing
a form which prompts them for the record selection criterion's/criteria's
values along with the updated values to be entered any of the remaining 8 or
9 fields in the underlying table.
let's say that the controls they could potentially use to select a record
are ("Study#" OR "IRB_Number") AND "MedRecNum". the PK in the table consists
of IRBNumber and MedRecNum (although Study# is mapped uniquely to IRBNumber).
there are some users who know that a MedRecNum is mapped to a Study# and
others who are more comfortable thinking of a MedRecNum mapped to its
IRB_Number so i want to try to keep this form general enough so that if they
input the value of one or the other plus the MedRecNum it will identify the
underlying record requiring updating.
assuming that this can be accomplished using SQL, i would want the user to
have the ability to update any or all of the remaining fields in the table
underlying the query.
i know that my WHERE clause in a query can filter for values in a form, e.g.
WHERE ((([Patients on Follow-Up].[Study#] = [Forms]![Query
Request]![Study#])));
and that the SET statement can accept the new values in the underlying
tables's
SET [Patients on Follow-Up][Pt Initials] = "ZZZ"
but can the where clause accept an 'OR' operator and can the SET statement
accept a statement like
SET [Forms]![Query Request]![Pt Init] = "ZZZ"
any SQL gurus out there care to opine?
-ted
i want to create an update query that will let my users modify records in a
table because when they have to scroll through their usual data entry form it
takes too long to get to the record they need modify and i think a query
would run a little quicker -- that's my assumption.
if you grant my assumption, then what i see as the way to implement it
(since they don't know how to use the Access QBE interface, is by developing
a form which prompts them for the record selection criterion's/criteria's
values along with the updated values to be entered any of the remaining 8 or
9 fields in the underlying table.
let's say that the controls they could potentially use to select a record
are ("Study#" OR "IRB_Number") AND "MedRecNum". the PK in the table consists
of IRBNumber and MedRecNum (although Study# is mapped uniquely to IRBNumber).
there are some users who know that a MedRecNum is mapped to a Study# and
others who are more comfortable thinking of a MedRecNum mapped to its
IRB_Number so i want to try to keep this form general enough so that if they
input the value of one or the other plus the MedRecNum it will identify the
underlying record requiring updating.
assuming that this can be accomplished using SQL, i would want the user to
have the ability to update any or all of the remaining fields in the table
underlying the query.
i know that my WHERE clause in a query can filter for values in a form, e.g.
WHERE ((([Patients on Follow-Up].[Study#] = [Forms]![Query
Request]![Study#])));
and that the SET statement can accept the new values in the underlying
tables's
SET [Patients on Follow-Up][Pt Initials] = "ZZZ"
but can the where clause accept an 'OR' operator and can the SET statement
accept a statement like
SET [Forms]![Query Request]![Pt Init] = "ZZZ"
any SQL gurus out there care to opine?
-ted