Menu
Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Newsgroup Archive
Access Newsgroups
Access Beginners
2 linked rookie Q's - filling fields and moving records
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Philip Herlihy" data-source="post: 1982686"><p>For the first one, try an "update query". First, make a query which</p><p>selects all the records you'd like to update. Then click the Query Type</p><p>button in the toolbar to turn it into an Update query, and put the date</p><p>- or something that returns today's date: =now() - into the "update to"</p><p>item for that field.</p><p></p><p>I'd question whether it's a good idea to move the records from one table</p><p>to another. If you ever need to search, you'd be searching two tables</p><p>instead of one. Why not leave them in place, and use an additional</p><p>field (how about DateSent) to distinguish these records? In general,</p><p>you'd have one table for one "type of thing" - makes life easier down</p><p>the road. If you had to do this (e.g. daft boss) then you'd want an</p><p>"append" query together with a corresponding "delete" query.</p><p></p><p>HTH</p><p></p><p>Phil, London</p></blockquote><p></p>
[QUOTE="Philip Herlihy, post: 1982686"] For the first one, try an "update query". First, make a query which selects all the records you'd like to update. Then click the Query Type button in the toolbar to turn it into an Update query, and put the date - or something that returns today's date: =now() - into the "update to" item for that field. I'd question whether it's a good idea to move the records from one table to another. If you ever need to search, you'd be searching two tables instead of one. Why not leave them in place, and use an additional field (how about DateSent) to distinguish these records? In general, you'd have one table for one "type of thing" - makes life easier down the road. If you had to do this (e.g. daft boss) then you'd want an "append" query together with a corresponding "delete" query. HTH Phil, London [/QUOTE]
Verification
Post reply
Forums
Archive
Newsgroup Archive
Access Newsgroups
Access Beginners
2 linked rookie Q's - filling fields and moving records
Top
