Good afternoon.
I'm trying to design a system in Access that exports with minimal user interaction/brainpower, but since there are more records to export than Excel 2003 can contain, the user will have to do some copying and pasting from a query.
While the user is doing that, I'd like to make sure they can't accidentally edit the query's data and therefore the underlying table's data.
Is there a way to design a query to stop the query from updating the table?
The solution would have to avoid changing the table to not be updatable because other things need to update it.
In searching these forums for an answer, I've heard the advice to use the DISTINCT statement in SQL for locking the query, but I'm not very good with SQL and I also can't have the side effect of the query having duplicates removed, which I think is the main point of the DISTINCT predicate.
If there's some easy way to get a query with zillions of records to export to XLS, that would be even better, but I'd still like to know for my own knowledge how to stop a query from editing a table.
Thanks.
-Nathan
I'm trying to design a system in Access that exports with minimal user interaction/brainpower, but since there are more records to export than Excel 2003 can contain, the user will have to do some copying and pasting from a query.
While the user is doing that, I'd like to make sure they can't accidentally edit the query's data and therefore the underlying table's data.
Is there a way to design a query to stop the query from updating the table?
The solution would have to avoid changing the table to not be updatable because other things need to update it.
In searching these forums for an answer, I've heard the advice to use the DISTINCT statement in SQL for locking the query, but I'm not very good with SQL and I also can't have the side effect of the query having duplicates removed, which I think is the main point of the DISTINCT predicate.
If there's some easy way to get a query with zillions of records to export to XLS, that would be even better, but I'd still like to know for my own knowledge how to stop a query from editing a table.
Thanks.
-Nathan