Export data based on date

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

How would I export the contents of an entire database based upon date the
data was entered? I need to build a function that could build a new database
of the data with respect to the date fields found in the records.

I then need to clean out the existing database of the record that where
exported to the new database.
 
Step away from the keyboard! You are almost certainly making a mistake. You
should never remove data from one database and pour it into another. About
the only exception is where you are nearing the 2GB Access database file size
limitation. Even that is probably a bad idea.

So why do you need to move data from one database to another? Maybe we can
find a better solution.
 
I inherited this database, and when it starts to slow down the users have
said that the previous developer would remove the old data in the database so
that the main forms would not load up all the records before showing the most
current entry.

Now I know your not to removed data or for that part split it and frankly
this database should be re-written to better utilize data calls on a already
congested network. But I just do not have the time to do this currently. So I
need a fix.

And about the best fix I could come up with was build a second database back
end with all the tables and references in place and just suck off the old
data and update it in the other database. I know this solution isn't in
keeping with proper database ediquette but hey until I can rebuild it I need
something to improve the responce time.

The intresting thing is this database isn't big, it is currently sitting at
about 65 Meg. And in the past I have seen databases that sit around this
value run horrible even with optimized data calls. Not really sure why that
was, but then again those where databases that where not optimized for
network flow (I inheritated also.)

Would this database run better sitting on a SQL server? Had considered
upscaling it but have run into snags with that too. Some of the tables refuse
to migrate.
 
Hi,

Upscaling a bad design to SQL Server would still leave you with a bad
design. Think Chevette 4-cylinder engine in a Corvette.

How about putting a Yes/No field named something like "ynActive" in the
appropriate tables. Make the default value Yes. When you no longer need to
see this record often, update the field to No. Next modifiy the queries that
use this table to exclude No's. That could speed things up.

The database might just need some tuning. Post the SQL of a slow form or
report. Maybe we can come up with some ideas.

Also test turning off the virus checker on the slower computers. Often that
is the cause. If there is an improvement, you might be able to set the virus
checker to not scan .md* or .accdb files.

If you want some more performance improvement ideas, Tony Toews has an
excellent web page on the subject. Check out:
http://www.granite.ab.ca/access/performancefaq.htm
 
Should of thought about the virus scanning issue, had trouble with that one
before.

Thank you for the suggestions. I think some qweaking of the forms with
respect to the data they are loading could greatly help. Was thinking about
that one last night, and instead of leading 87000 records could only load and
refresh 7000 records.

I will look into this.

Thank you.
 
Is there a way to filter out the records over the past 3 years? How would I
incorporate that into a SQL statement?
 
Back
Top