arotgans Posted November 27, 2000 Posted November 27, 2000 Hi All, For our newsroom I wrote a 'planningsdatabase', containing all events happening in the world which are relevant for our radiostation. It all works flawless, and now I'm working on the archive-side of the system. I want to be able to keep the records/events which are expired, but not in the database our users can access at first. Due to the large amount of records, this will be slowing down the system to much. I tried to export all those expired records, but there is no 'append'-option, so every export has to go to it's own file. And that's not what I want, I'd like to have 1 archive-database. Is there a way to handle this problem, or does someone have another idea how to do this ? (I tried omitting all records expired, but there are many filters/searches used in the database, and they conflict with the omittingfilter) Kind regards, Andr
dspires Posted November 27, 2000 Posted November 27, 2000 Work it in the other direction. In the current database, do a find to get the records to export, then open the archive database and import the found set from the current database. Lastly, delete the records in the found set from the current database. You can also write a script to take care of this stuff (remember to change to single-user before running though).
Recommended Posts
This topic is 8766 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now