C
Carmen
Hi,
I currently have a table with the last column being PRIORITY. I've created
about 26 update queries to populate this field based on different criteria.
It's a nightmare to make changes or explain this to a person with little
Access knowledge. THus I'm trying to write some code to populate the table
instead.
I have little knowledge on recordsets, but I know to open the recordset I
have to provide an sql statement. Can this sql statement be replaced with
the sql from the update queyr? I'm having problems with the replacement. In
the update query sql, it shows that I have "update....left
join....on......as.....Set....Where...." I understand that this sql will at
the same time populate the table so I'm not sure if it can be used in the
open recordset.
I have many many tables to prioritize and each one has its own criteria. My
initial thought was to set up an array for each report that will capture the
priority numbers, and the sqls to open and update (at the same time). This
is then run through a generic procedure.
Please let me know if I'm just too optimistic and can't be done this way.
Thanks,
Carmen
I currently have a table with the last column being PRIORITY. I've created
about 26 update queries to populate this field based on different criteria.
It's a nightmare to make changes or explain this to a person with little
Access knowledge. THus I'm trying to write some code to populate the table
instead.
I have little knowledge on recordsets, but I know to open the recordset I
have to provide an sql statement. Can this sql statement be replaced with
the sql from the update queyr? I'm having problems with the replacement. In
the update query sql, it shows that I have "update....left
join....on......as.....Set....Where...." I understand that this sql will at
the same time populate the table so I'm not sure if it can be used in the
open recordset.
I have many many tables to prioritize and each one has its own criteria. My
initial thought was to set up an array for each report that will capture the
priority numbers, and the sqls to open and update (at the same time). This
is then run through a generic procedure.
Please let me know if I'm just too optimistic and can't be done this way.
Thanks,
Carmen